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. Althou…

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

X-www-urlencoded not supported(?)

sancroth (Nick) November 17, 2017, 12:46pm 3

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?

Topic		Replies	Views
"error" : "Content-Type header [application/x-www-form-urlencoded] is not supported", Elasticsearch	6	14633	June 9, 2020
Curl XPOST errors not supported 406 Elasticsearch	4	6648	April 27, 2020
ES is giving error Elasticsearch	3	363	November 23, 2018
Curl via script: Content-Type header [application/x-www-form-urlencoded] is not supported","status":406}curl: (6) Could not resolve host: application Elasticsearch	3	3098	January 16, 2018
error":"Content-Type header [application/x-www-form-urlencoded] is not supported","status":406 Elasticsearch	3	23562	February 11, 2019

X-www-urlencoded not supported(?)

Related topics