tree 521e3d2ddde3d1ca53b365e907a37d252c13a769
parent befcf7031d79298ab68c0d19ba77fa991aa9f024
author Frédéric Lécaille <flecaille@haproxy.com> 1662652416 +0200
committer Frédéric Lécaille <flecaille@haproxy.com> 1662653098 +0200

MINOR: h3: Send the h3 settings with others streams (requests)

This is the ->finalize application callback which prepares the unidirectional STREAM
frames for h3 settings and wakeup the mux I/O handler to send them. As haproxy is
at the same time always waiting for the client request, this makes haproxy
call sendto() to send only about 20 bytes of stream data. Furthermore in case
of heavy loss, this give less chances to short h3 requests to succeed.

Drawback: as at this time the mux sends its streams by their IDs ascending order
the stream 0 is always embedded before the unidirectional stream 3 for h3 settings.
Nevertheless, as these settings may be lost and received after other h3 request
streams, this is permitted by the RFC.

Perhaps there is a better way to do. This will have to be checked with Amaury.

Must be backported to 2.6.