X-www-urlencoded not supported(?)

I am using an extension from a testing framework that is supposed to build up some indices and fill them with data on my elastic server.

The extension works perfectly well with a demo server that the company behind the extension gives us access to, containing just an elasticsearch instance.
Although when we target our elasticsearch server we get the error of :
application/x-www-form-urlencoded not supported.

That got me thinkng and used some more advanced queries though curl:
The simple curl "http://136.243.xx.xx:9200/ returns :
"name" : "Artorias",
"cluster_name" : "some name",
"cluster_uuid" : "some uid",
"version" : {
"number" : "6.0.0",
"build_hash" : "8f0685b",
"build_date" : "2017-11-10T18:41:22.859Z",
"build_snapshot" : false,
"lucene_version" : "7.0.1",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
"tagline" : "You Know, for Search"

Then trying out a query like :
curl "http:-XGET 'http://136.243.xx.xx:9200/_cat/indices?v&pretty'
curl "http://136.243.xx.xx:9200/_search" -d '{"query": {"match_all": {}}}'

return :

{"error":"Content-Type header [application/x-www-form-urlencoded] is not supported","status":406}

Could some http.cors directive help solve this?(i am still reading about this).

Hints to any direction? :slight_smile:

This blog post covers the changes made to content type handling.


You are great.

So if i understand correct they either got to change the way the extension sets it's headers to the correct type, or downgrade to 5.x and allow bad contet-type use to get through.Right? :stuck_out_tongue:

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.