You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Versions 4.x to access Elasticsearch (not officially supported) it is necessary to set compatibility headers; we have this documented. But in addition to the headers defined in the client configuration, the reactive client sets a content-type: application/json on request with a body. This lead to two headers being sent and Elasticsearch rejects this.
So the config defined headers must have higher priority and overwrite an automatically set header.
The text was updated successfully, but these errors were encountered:
When using Versions 4.x to access Elasticsearch (not officially supported) it is necessary to set compatibility headers; we have this documented. But in addition to the headers defined in the client configuration, the reactive client sets a
content-type: application/json
on request with a body. This lead to two headers being sent and Elasticsearch rejects this.So the config defined headers must have higher priority and overwrite an automatically set header.
The text was updated successfully, but these errors were encountered: