mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-08-10 00:57:02 +02:00
ef2b15998c
There is a mechanisme in the H1 and H2 multiplexer to skip the payload when a response is returned to the client when it must not contain any payload (response to a HEAD request or a 204/304 response). However, this does not work when the splicing is used. The H2 multiplexer does not support the splicing, so there is no issue. But with the mux-h1, when data are sent using the kernel splicing, the mux on the server side is not aware the client side should skip the payload. And once the data are put in a pipe, there is no way to stop the sending. It is a defect of the current design. This will be easier to deal with this case when the mux-to-mux forwarding will be implemented. But for now, to fix the issue, we should add an HTX flag on the start-line to pass the info from the client side to the server side and be able to disable the splicing in necessary. The associated reg-test was improved to be sure it does not fail when the splicing is configured. This patch should be backported as far as 2.4.. |
||
|---|---|---|
| .. | ||
| haproxy | ||
| import | ||
| make | ||