tree 6563a67c0d54c2e6ea8e733c70c9f381806316c8
parent a88e8bf4283cea6d21eb88ba819316185e1c3465
author Amaury Denoyelle <adenoyelle@haproxy.com> 1657293580 +0200
committer Amaury Denoyelle <adenoyelle@haproxy.com> 1657549312 +0200

BUG/MEDIUM: mux-quic: fix server chunked encoding response

QUIC MUX was not able to correctly deal with server response using
chunked transfer-encoding. All data will be transfered correctly to the
client but the FIN bit is missing. The transfer will never stop as the
client will wait indefinitely for the FIN bit.

This bug happened because the HTX message representing a chunked encoded
payload contains a final empty block with the EOM flag. However,
emission is skipped by QUIC MUX if there is no data to transfer. To fix
this, the condition was completed to ensure that there is no need to
send the FIN signal. If this is false, data emission will proceed even
if there is no data : this will generate an empty QUIC STREAM frame with
FIN set which will mark the end of the transfer.

To ensure that a FIN STREAM frame is sent only one time,
QC_SF_FIN_STREAM is resetted on send confirmation from the transport in
qcc_streams_sent_done().

This bug was reproduced when dealing with chunked transfer-encoding
response for the HTTP server.

This must be backported up to 2.6.