mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-12 00:39:32 +00:00
haproxy public development tree
a33ff7a8a7
When an appctx is created on the server side, we now set the corresponding conn-stream to ready state (CS_ST_RDY). When it happens, the backend conn-stream is in CS_ST_INI state. It is not consistant to let the conn-stream in this state because it means it is possible to have a target installed in CS_ST_INI state, while with a connection, the conn-stream is switch to CS_ST_RDY or CS_ST_EST state. It is especially anbiguous because we may be tempted to think there is no endpoint attached to the conn-stream before the CS_ST_CON state. And it is indeed the reason for a bug leading to a crash because a cs_detach_endp() is performed if an abort is detected on the backend conn-stream in CS_ST_INI state. With a mux or a appctx attached to the conn-stream, "->endp" field is set to NULL. It is unexpected. The API will be changed to be sure it is not possible. But it exposes a consistency issue with applets. So, the conn-stream must not stay in CS_ST_INI state when an appctx is attached. But there is no reason to set it in CS_ST_REQ. The conn-stream must be set to CS_ST_RDY to handle applets and connections in the same way. Note that if only the target is set but no appctx is created, the backend conn-stream is switched from CS_ST_INI to CS_ST_REQ state to be able to create the corresponding appctx. This part is unchanged. This patch depends on the commit "MINOR: backend: Don't allow to change backend applet". The ambiguity exists on previous versions. But the issue is 2.6-specific. Thus, no backport is needed. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .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)