mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-08-11 01:26:58 +02:00
The whole QUIC stack is impacted by this change : * at quic-conn level, a single function is now used to handle uni and bidirectional streams. It uses qcc_recv() function from MUX. * at MUX level, qc_recv() io-handler function does not skip uni streams * most changes are conducted at app layer. Most notably, all received data is handle by decode_qcs operation. Now that decode_qcs is the single app read function, the H3 layer can be simplified. Uni streams parsing was extracted from h3_attach_ruqs() to h3_decode_qcs(). h3_decode_qcs() is able to deal with all HTTP/3 frame types. It first check if the frame is valid for the H3 stream type. Most notably, SETTINGS parsing was moved from h3_control_recv() into h3_decode_qcs(). This commit has some major benefits besides removing duplicated code. Mainly, QUIC flow control is now enforced for uni streams as with bidi streams. Also, an unknown frame received on control stream does not set an error : it is now silently ignored as required by the specification. Some cleaning in H3 code is already done with this patch : h3_control_recv() and h3_attach_ruqs() are removed as they are now unused. A final patch should clean up the unneeded remaining bit. |
||
---|---|---|
.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 | ||
ROADMAP | ||
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)