mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-16 06:11:00 +01:00
4dee110f56
A client may send multiple INITIAL packets if ClientHello is too big for only one. In case a Retry token is used, the client must reuse it for every INITIAL packets. On the haproxy server side, there was an inconsistency to handle these packets depending on the socket mode : * when using listener socket, token is always revalidated. * when using connection socket, token check is bypassed. This is because quic_conn instance is known through its socket and thus quic_rx_pkt_retrieve_conn() is not necessary. RFC 9000 does not seems to mandate retry token validation after the first INITIAL packet per connection. Thus, this patch chooses to bypass the check every time the connection instance is known, as this indicates that a previous token was already validated. This should be backported up to 2.7.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)