4038b94706
When receiving additional data while chaining multiple tcp-check expects, previous inverse expects might have a different result with the new data. They need to be evaluated again against the new data. Add a pointer to the first inverse expect rule of the current expect chain (possibly of length one) to each expect rule. When receiving new data, the currently evaluated tcp-check rule is set back to this pointed rule. Fonctionnaly speaking, it is a bug and it exists since the introduction of the feature. But there is no way for now to hit it because when an expect rule does not match, we wait for more data, independently on the inverse flag. The only way to move to the following rule is to be sure no more data will be received. This patch depends on the commit "MINOR: mini-clist: Add functions to iterate backward on a list". [Cf: I slightly updated the patch. First, it only concerns inverse expect rule. Normal expect rules are not concerned. Then, I removed the BUG tag because, for now, it is not possible to move to the following rule when the current one does not match while more data can be received.]
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)