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

@shamsimam wrote:

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

$ curl http://localhost:8080/content.js
...
< HTTP/1.1 200 OK
< Content-Type: application/javascript
< Content-Length: 1234567
...

Example: request to via haproxy (note content-length header is dropped and transfer-encoding is introduced)

$ curl http://localhost:9090/some.js
...
< HTTP/1.1 200 OK
< content-type: application/javascript
< transfer-encoding: chunked
...

Our tuning parameters in haproxy.cfg:

tune.maxrewrite 32768
tune.bufsize 65536

Posts: 1

Participants: 1

Read full topic