243bc95de0
Since the following commit, MUX H2 timeout function has been slightly exetended. d38d8c6ccb189e7bc813b3693fec3093c9be55f1 BUG/MEDIUM: mux-h2: make sure control frames do not refresh the idle timeout A side-effect of this patch is that now backend idle connection expire timer is not reset if already defined. This means that if a timer was registered prior to the connection transition to idle, the connection would be destroyed on its timeout. If this happens for enough connection, this may have an impact on the reuse rate. In practice, this case should be rare, as h2c timer is set to TICK_ETERNITY while there is active streams. The timer is not refreshed most of the time before going the transition to idle, so the connection won't be deleted on expiration. The only case where it could occur is if there is still pending data blocked on emission on stream detach. Here, timeout server is applied on the connection. When the emission completes, the connection goes to idle, but the timer will still armed, and thus will be triggered on the idle connection. To prevent this, explicitely reset h2c timer to TICK_ETERNITY for idle backend connection via h2c_update_timeout(). This patch is explicitely not scheduled for backport for now, as it is difficult to estimate the real impact of the previous code state.
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.