0e09cce0fd
Since 2.9, it is possible to drain the request payload from the H1 multiplexer in case of early reply. When this happens, the upper stream is detached but the H1 stream is not destroyed. Once the whole request is drained, the end of the detach stage is finished. So the H1 stream is destroyed and the H1 connection is ready to be reused, if possible, otherwise it is released. And here is the issue. If some data of the next request are received with last bytes of the drained one, parsing of the next request is immediately started. The previous H1 stream is destroyed and a new one is created to handle the parsing. At this stage the H1 connection may be released, for instance because of a parsing error. This case was not properly handled. Instead of immediately exiting the mux, it was still possible to access the released H1 connection to refresh its timeouts, leading to a UAF issue. Many thanks to Annika for her invaluable help on this issue. The patch should fix the issue #2602. It must be backported as far as 2.9.
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.