mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-04-11 03:31:36 +00:00
haproxy public development tree
In si_cs_recv(), when a shutdown for reads is handled, the conn-stream may be closed. It happens when the ouput channel is closed for writes or if SI_FL_NOHALF is set on the stream-interface. In this case, conn-stream's flags are reset. Thus, if an error (CS_FL_ERROR) or an end of input (CS_FL_EOI) is reported by the mux, the event is lost. si_cs_recv() does not report these events by itself. It relies on si_cs_process() to report them to the stream-interface and/or the channel. For instance, if CS_FL_EOS and CS_FL_EOI are set by the H1 multiplexer during a call to si_cs_recv() on the server side, if the conn-stream is closed (read0 + SI_FL_NOHALF), the CS_FL_EOI flag is lost. Thus, this may lead the stream to interpret it as a server abort. Now, conn-stream's flags are processed at the end of si_cs_recv(). The function is responsible to set the right flags on the stream-interface and/or the channel. Due to this patch, the function is now almost linear. Except some early checks at the beginning, there is only one return statement. It also fixes a potential bug because of an inconsistency between the splicing and the buffered receipt. On the first case, CS_FL_EOS if handled before errors on the connection or the conn-stream. On the second one, it is the opposite. This patch must be backported to 2.0 and 1.9. |
||
---|---|---|
.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)