mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 23:01:24 +02:00
89e34c261b
Because si_cs_process() is also the SI wake callback function, it may be called from the mux layer. Thus, in such cases, it is performed outside any I/O event and si_cs_recv() is not called. If a read0 is reported by the mux, via the CS_FL_EOS flag, the event is not handled, because only si_cs_recv() take care of this flag for now. It is not a bug, because this does not happens for now. All muxes set this flag when the data layer retrieve data (via mux->rcv_buf()). But it is safer to be prepared to handle it from the wake callback. And in fact, it will be useful to fix the HTTP upgrades of TCP connections (especially TCP>H1>H2 upgrades). To be sure to not handle the same event twice, it is only handled if the shutr is not already set on the input channel.
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)