mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-18 11:40:50 +00:00
haproxy public development tree
0bb5a5c4b5
If a receipt ends with the HTX buffer full and everything is completed except appending the HTX EOM block, we end up detecting an error because the H1 parser did not switch to H1_MSG_DONE yet while all conditions for an end of stream and end of buffer are met. This can be detected by retrieving 31532 or 31533 chunk-encoded bytes over H1 and seeing haproxy log "SD--" at the end of a successful transfer. Ideally the EOM part should be totally independent on the H1 message state since the block was really parsed and finished. So we should switch to a last state requiring to send only EOM. However this needs a few risky changes. This patch aims for simplicity and backport safety, thus it only adds a flag to the H1 stream indicating that an EOM is still needed, and excludes this condition from the ones used to detect end of processing. A cleaner approach needs to be studied, either by adding a state before DONE or by setting DONE once the various blocks are parsed and before trying to send EOM. This fix must be backported to 2.0. The issue does not seem to affect 1.9 though it is not yet known why, probably that it is related to the different encoding of trailers which always leaves a bit of room to let EOM be stored. |
||
|---|---|---|
| .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)