7d554ca629
Haproxy QUIC stack suffers from a limitation : it's not possible to emit a packet which contains probing data and a ACK frame in it. Thus, in case qc_do_build_pkt() is invoked which both values as true, probing has the priority and ACK is ignored. However, this has the undesired side-effect of possibly generating two coalesced packets of the same type in the same datagram : the first one with the probing data and the second with an ACK frame. This is caused by qc_prep_pkts() loop which may call qc_do_build_pkt() multiple times with the same QEL instance. This case is normally use when a full datagram has been built but there is still content to emit on the current encryption level. To fix this, alter qc_prep_pkts() loop : if both probing and ACK is requested, force the datagram to be written after packet encoding. This will result in a datagram containing the packet with probing data as final entry. A new datagram is started for the next packet which will can contain the ACK frame. This also has some impact on INITIAL padding. Indeed, if packet must be the last due to probing emission, qc_prep_pkts() will also activate padding to ensure final datagram is at least 1.200 bytes long. Note that coalescing two packets of the same type is not invalid according to QUIC RFC. However it could cause issue with some shaky implementations, so it is considered as a bug. This must 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 | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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.