Running query with embedded "%" sign causes "internal server error"

[ccurvey]

Kibana version:

5.x

Elasticsearch version:

5.3.0

Server OS version:

??

Browser version:

Firefox 50

Browser OS version:

Fedora 23 (Qubes version)

Original install method (e.g. download page, yum, from source, etc.):

None. Using Elastic Cloud/X-Pack

Description of the problem including expected versus actual behavior:

Running query with embedded "%" sign causes "internal server error"

Steps to reproduce:

1. Run this query:

q = '''
{
    "size" : 20,
    "query" : {
        "bool" : {
            "must" : {
                "multi_match" : {
                    "fields" : ["text", "title"],
                    "query" : "Donald Trump",
                    "fuzziness": "1",
                    "prefix_length": "4",
                    "max_expansions" : "5",
                    "minimum_should_match": "3<90%"
                }
            }
   
  }
}

2. You will get an internal server error
3. Run the same query, removing the "minimum_should_match" clause. You'll get results.

For further background, see https://discuss.elastic.co/t/query-works-through-python-interface-fails-in-kibana/82423

[lukasolson]

Are you running this query in Console, or Discover? I'm not getting the same error in either place.

[ccurvey]

I'm running it in what used to be called "Sense"...I'm not sure what it is called now in X-Pack-Land :)

Incidentally, the query works fine if submitted via a Python program or CURL, so it's something to do with the [whatever we are calling Sense now] interface.

[jbudz]

@AlexP-Elastic are you expecting POST bodies with content-type application/json to be url encoded?

[AlexP-Elastic]

I just tried to reproduce this in 5.3.1 on EC using Console and unlike in the issue @ccurvey ran into, the query gets posted in the body via <host etc>/api/console/proxy?uri=_search

Whereas @ccurvey reported the following endpoint: <host etc>/api/console/proxy?uri=<encoded _search URI>&<JSON-body-incorrectly-URL-encoded>

@jbudz or @lukasolson is there any way that Kibana can "decide" (eg based on OS or browser or something else?) to try to put the body encoded in the URL as per this copy/paste from the dev console: https://discuss.elastic.co/t/query-works-through-python-interface-fails-in-kibana/82423/12? (it's definitely not something Elastic Cloud is doing?)

[AlexP-Elastic]

Ah OK I've investigated further and can now "reproduce": GET _search works (ie includes a separate body) but if I then replace GET with get (lower case) then the failure occurs .. an unobtrusive error is shown next to the get but the "play" button doesn't go away (unlike if you just paste the whole request in directly, when the "play" button disappears)

So the issue (if there is one) seems to be error handling? (ie the "play" button should go away)

(The lower case version of the verb is used incidentally, despite the error, eg post works identically to POST ditto put and PUT, it's just get that behaves differently)

For completeness here's the full thing I pasted into console to get it to fail:

GET _search
{
    "size" : 20,
    "query" : {
        "bool" : {
            "must" : {
                "multi_match" : {
                    "fields" : ["text", "title"],
                    "query" : "Donald Trump",
                    "fuzziness": "1",
                    "prefix_length": "4",
                    "max_expansions" : "5",
                    "minimum_should_match": "3<90%"
                }
            }
      }
  }
}

then replace GET with get

[jbudz]

Great, tracking at #8832. We have #14327 opened to address this.