We’re trying to use HAProxy in an application where the client captures voice clips and submits them as part of an HTTP POST. We have Transfer-Encoding set to chunked because the voice clips can be quite large, and frankly because the customer requires it. That is how it arrives at HAProxy, but on the backend the request is no longer chunked. Can anyone tell me what I’m doing wrong? Is there a setting to propagate Transfer-Encoding?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Chunked transfer encoding in haproxy | 7 | 3681 | April 16, 2020 | |
| Disable haproxy converting responses with content-length header to chunked transfer-encoding | 4 | 2925 | July 22, 2019 | |
| 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 | 0 | 469 | April 27, 2021 | |
| Curl not closed when 204 No-Content and Transfer-Encoding: chunked through haproxy | 1 | 1437 | August 27, 2017 | |
| Extremely Large HTTP Responses with Chunked Encoding Blocked | 4 | 1761 | January 22, 2021 |