8633446337
Dedicated HTTP/2 stats proxy counters are available for current and total number of HTTP/2 connection on both frontend and backend sides. Both counters are simply incremented into h2_init(). This causes issues when using reverse HTTP. First, increment is not performed on the expected side, as it is triggered before h2_conn_reverse() which switches a connection from frontend to backend or vice versa. For example on active revers side, h2_total_connections is incremented on the backend only even after connection is reversed and attached to a listener for the remainder of its lifetime. h2_open_connections suffers from a similar but arguably worst behavior as it is also decremented. If increment and decrement operations are not performed on the same proxy side, which happens for every connection which has been successfully reversed, it causes an invalid counter value, possibly with an integer overflow. To fix this, delay increment operations on reverse HTTP from h2_init() to h2_conn_reverse(). Both counters are updated only after reverse has completed, thus using the expected frontend or backend side. To prevent overflow on h2_open_connections, ensure h2_release() decrement is not performed if a connection is freed before achieving its reversal, as in this case it would not have been accounted by H2 counters. This should be backported up to 2.9. This should fix github issue #2821. |
||
|---|---|---|
| .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.