mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-20 00:10:41 -05:00
HAProxy - Load balancer
0933c7b3c8
As specified by RFC 9000, it is forbidden to send a CONNECTION_CLOSE of type 0x1d (CONNECTION_CLOSE_APP) in an Initial or Handshake packet. It must be converted to type 0x1c (CONNECTION_CLOSE) with APPLICATION_ERROR code. CONNECTION_CLOSE_APP are generated by QUIC MUX interaction. Thus, special care must be taken when dealing with a 0-RTT packet, as this is the only case where the MUX can be instantiated and quic-conn still on the Initial or Handshake encryption level. To enforce RFC 9000, xprt build packet function is now responsible to translate a CONNECTION_CLOSE_APP if still on Initial/Handshake encryption. This process is done in a dedicated function named qc_build_cc_frm(). Without this patch, BUG_ON() statement in qc_build_frm() will be triggered when building a CONNECTION_CLOSE_APP frame on Initial or Handshake level. This is because QUIC_FT_CONNECTION_CLOSE_APP frame builder mask does not allow these encryption levels, as opposed to QUIC_FT_CONNECTION_CLOSE builder. This crash was reproduced by modifying the H3 layer to force emission of a CONNECTION_CLOSE_APP on first frame of a 0-RTT session. Note however that CONNECTION_CLOSE emission during Handshake is a complicated process for the server. For the moment, this is still incomplete on haproxy side. RFC 9000 requires to emit it multiple times in several packets under different encryption levels, depending on what we know about the client encryption context. This patch should be backported up to 2.6. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)