500 error on slash in query #2372
Closed
Comments
Additional request. Would be great if the frontend shows that there was a 500 error instead of hanging in Loading... Now i had to find out using Dev-Tools / Firebug what the issue was. |
edmundoa
added a commit
that referenced
this issue
Jul 4, 2016
When the search query contains an unescaped slash, calling to `generateParseException()` throws a NullPointerException. We solve it by catching the exception and let the normal program flow to continue, which at that point will return the syntax error. Fixes #2372
edmundoa
added a commit
that referenced
this issue
Jul 4, 2016
When the search query contains an unescaped slash, calling to `generateParseException()` throws a NullPointerException. We solve it by catching the exception and let the normal program flow to continue, which at that point will return the syntax error. Fixes #2372
joschi
added a commit
that referenced
this issue
Jul 11, 2016
When the search query contains an unescaped slash, calling to `generateParseException()` throws a NullPointerException. We solve it by catching the exception and let the normal program flow to continue, which at that point will return the syntax error. Fixes #2372
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
When searching something with a forward-slash
/
but that is not escaped, the web ui keeps hanging in aloading...
state. I would expect malformed syntax feedback.Steps to reproduce the problem
/search?rangetype=relative&fields=message%2Csource&width=1879&highlightMessage=&relative=300&q=bla%3A%2Ffoo
Environment
The text was updated successfully, but these errors were encountered: