337243235f
In the H2 mux, when a empty DATA frame is used to finish a message, just to set the ES flag, we now only set the EOM flag on the HTX message. However, if the HTX message is empty, this event will not be properly handled on the other side because there is no effective data to handle. Thus, it is interpreted as an abort by the H1 mux. It is in part caused by the current H1 mux design but also because there is no way to emit empty HTX block (NOOP HTX block) or to wakeup a mux for send when there is no data to finish some internal processing. Thus, for now, to work around this limitation, an EOT HTX block is added by the H2 mux if a EOM flag is added on an empty HTX message. This case is only possible when an empty DATA frame with the ES flag is received. This fix is specific for 2.4. No backport needed. |
||
|---|---|---|
| .github | ||
| contrib | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
README
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)