7885a3b3e1
Recently, an issue was found with QUIC zero-copy forwarding on 3.0 version. A desynchronization could occur internally in QCS Tx bytes counters which would cause a BUG_ON() crash on qcs_destroy() when the stream is detached. It was silently fixed in version 3.1 by the following patch. As it was considered as an optimization, it was not scheduled yet for backport. 6697e87ae5e1f569dc87cf690b5ecfc049c4aab0 MINOR: mux-quic: Don't send an emtpy H3 DATA frame during zero-copy forwarding This mistake has been caused due to some counter-intuitive manipulation in QUIC zero-copy implementation. Try to streamline this in QUIC MUX done_ff callback and its application protocol counterpart. Especially for values exchanged between MUX and application on one side, and MUX and stconn layer as done_fastfwd return value. First, application done_ff callback now returns the length of the wholly encoded frame. For HTTP/3, it means header length + payload length h3 frame. This value can then be reused as qcc_send_stream() argument to increase QCS Tx soft offset. As previously, special care has been taken to ensure that QUIC MUX done_ff only return the transferred data bytes. Thus, any extra offset for HTTP/3 header is properly excluded. This is mandatory for stconn layer to consider the transfer has completed. Secondly, remove duplicated code in application done_ff to reset iobuf info. This is now factorize in QUIC MUX done_ff itself. This patch is related to github issue #2678.
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.