mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-17 01:28:32 -05:00
HAProxy - Load balancer
c2ea47fb18
Alexandre Derumier reported issue #308 in which the client timeout will strike on an H2 mux when it's shorter than the server's response time. What happens in practice is that there is no activity on the connection and there's no data pending on output so we can expire it. But this does not take into account the possibility that some streams are in fact waiting for the data layer above. So what we do now is that we enforce the timeout when: - there are no more streams - some data are pending in the output buffer - some streams are blocked on the connection's flow control - some streams are blocked on their own flow control - some streams are in the send/sending list In all other cases the connection will not timeout as it means that some streams are actively used by the data layer. This fix must be backported to 2.0, 1.9 and probably 1.8 as well. It depends on the new "blocked_list" field introduced by "MINOR: mux-h2: add a per-connection list of blocked streams". It would be nice to also backport "ebtree: make eb_is_empty() and eb_is_dup() take a const" to avoid a build warning. |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| contrib | ||
| doc | ||
| ebtree | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitignore | ||
| .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)