mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-24 04:11:02 +01:00
2e60aa4dee
When a script is executed, it is not always allowed to yield. Lua sample fetches and converters cannot yield. For lua actions, it depends on the context. When called from tcp content ruleset, an action may yield until the expiration of the inspect-delay timeout. From http rulesets, yield is not possible. Thus, when channel functions (dup, get, append, send...) are called, instead of yielding when it is not allowed and triggering an error, we just give up. In this case, some functions do nothing (dup, append...), some others just interrupt the in-progress job (send, forward...). But, because these functions don't yield anymore when it is not allowed, the script regains the control and can continue its execution. This patch depends on "MINOR: lua: Add a flag on lua context to know the yield capability at run time". Both may be backported in all stable versions. However, because nobody notice this bug till now, it is probably not necessary, excepted if someone ask for it.
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)