We are noticing haproxy sometimes converts responses with content-length headers to responses with chunked transfer-encoding and no content length headers. Is it possible to disable this behavior and always have haproxy respect the backend response headers? Example: request to backend directly $ c…

I doubt haproxy will do that by default. Please share the entire headers, the entire configuration as well as the output of haproxy -vv. You probably have some feature enabled that transform the payload, like compression.

I was unable to quickly reproduce this with a simple Python server. My actual server is a Jetty server, I will debug the Jetty server further and see if Jetty is responsible here. I’ll update this issue with my findings.

Disable haproxy converting responses with content-length header to chunked transfer-encoding

Help!

shamsimam July 22, 2019, 2:38pm 5

I confirmed that the chunked to non-chunked conversion is happening at my Jetty server/client. Sorry for the invalid request.

Topic		Replies	Views
Chunked transfer encoding in haproxy Help!	7	4277	April 16, 2020
Haproxy removing Content-Length header if Transfer-Encoding header is found Help!	2	1267	January 20, 2022
Curl not closed when 204 No-Content and Transfer-Encoding: chunked through haproxy Help!	1	1493	August 27, 2017
Haproxy 2.0.2x, HTTP/2 sends only a small amount of data when it receives an HTTP/1.1 chunk response from the backend Help!	0	555	April 27, 2021
Extremely Large HTTP Responses with Chunked Encoding Blocked Help!	4	2255	January 22, 2021

Disable haproxy converting responses with content-length header to chunked transfer-encoding

Related topics