Skip to content

[4.x] Prefer config supplied content-type and accept header in reactive client. #2327

@sothawo

Description

@sothawo

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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions