mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 22:01:31 +02:00
a1ab97316f
In connect_server(), if there were already a CS assosciated with the stream, but we can't reuse it, because the target is different (because we tried a previous connection, it failed, and we use redispatch so we switched servers), don't forget to set srv_cs to NULL. Otherwise, if we end up reusing another connection, we would consider we already have a conn_stream, and we won't create a new one, so we'd have a new connection but we would not be able to use it. This can explain frozen streams and connections stuck in CLOSE_WAIT when using redispatch. This should be backported to 1.9 and 2.0.
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)