mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-27 20:01:15 -05:00
HAProxy - Load balancer
dfd1301035
We rely on <conn_opening> stats counter and tune.quic.retry_threshold setting to dynamically start sending Retry packets. We continue to send such packets when "quic-force-retry" setting is set. The difference is when we receive tokens. We check them regardless of this setting because the Retry could have been dynamically started. We must also send Retry packets when we receive Initial packets without token if the dynamic Retry threshold was reached but only for connection which are not currently opening or in others words for Initial packets without connection already instantiated. Indeed, we must not send Retry packets for all Initial packets without token. For instance a client may have already sent an Initial packet without receiving Retry packet because the Retry feature was not started, then the Retry starts on exeeding the threshold value due to others connections, then finally our client decide to send another Initial packet (to ACK Initial CRYPTO data for instance). It does this without token. So, for this already existing connection we must not send a Retry packet. |
||
|---|---|---|
| .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)