Hello, we're troubleshooting issue in communication between client and elastic 8.13 in between with HAProxy. Is it correct to response to HEAD request with EMPTY "transfer-encoding: chunked"? In other words - to HEAD request to elastic API, the response is "transfer-encoding: chunked" without any d…

we have fixed bugreport on haproxy - haproxy partially forwards transfer-encoding from backend in response to a HEAD request · Issue #2836 · haproxy/haproxy · GitHub

Is it correct to response to HEAD req from elastic API with empty "transfer-encoding: chunked"?

Elastic Stack Elasticsearch

DavidTurner (David Turner) January 13, 2025, 9:20am 4

No, that's not the case. HEAD requests are special in this regard. See e.g. RFC 9112 §6.3:

Any response to a HEAD request [...] is always terminated by the first empty line after the header fields, regardless of the header fields present in the message, [...]

Topic		Replies	Views
HEAD no longer works in 5.4.1 Elasticsearch	3	1123	July 12, 2017
Metricbeat HTTP module - request and process headers only Beats beats-module	2	460	June 21, 2020
TooLongFrameException: HTTP header is larger than 8192 bytes Elasticsearch	5	5286	July 6, 2017
Metricbeat HTTP module - custom request and fetch headers only Beats beats-module , metricbeat	2	422	June 26, 2020
Truncated Chunk Elasticsearch language-clients	3	60	August 20, 2025

Is it correct to response to HEAD req from elastic API with empty "transfer-encoding: chunked"?

Related topics