c0c3a325a4
When stream detach callback is called, the default behavior is to free the associated QCS instance. However, QCS may be preserved in so-called detached state if there is remaining data to sent. This condition is checked via qcs_is_close_local() which ensures that either FIN or a RESET_STREAM was emitted. However, this does not take into account a scheduled STOP_SENDING emission, which can happen in case of request abort for example. Adjusts qcm_strm_detach() to also take into account STOP_SENDING emission before freeing or keeping a detached QCS instance. As a complement, QCS have to be purged after STOP_SENDING emission when reaching completion. On frontend side, this bug is probably only visible in case of HTTP/3 POST. When dealing with GET, FIN is most of the time received earlier, which render STOP_SENDING unnecessary. This issue however has a bigger impact on the backend side. In case of stream abort, for example on timeout, the server may be left unnotified and will continue to emit STREAM data despite QCS closure on haproxy client side. Note that this fix also has a side effect on backend connection reuse. Indeed it may increase the rate of QCS in detached state. This may prevent an idle connection to be reinserted in the server pool, without any possibility to reinsert it later. In the end this causes a lower reuse rate. This is an issue which must be addressed in a dedicated patch. For now, add a COUNT_IF_HOT() to report when such situation occurs. This should be backported to all stable releases, after a period of observation. COUNT_IF_HOT() is unnecessary on 3.2 and below. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .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.