mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-05-17 11:16:11 +02:00
19a69b3740
A wrong behavior was introduced by e9544935e86278dfa3d49fb4b97b860774730625, leading to preventing loading any configuration where a capture slot id is used in a backend. IE, the configuration below does not parse: frontend f bind *:80 declare capture request len 32 default_backend webserver backend webserver http-request capture req.hdr(Host) id 1 The point is that such type of configuration is valid and should run. This patch enforces the check of capture slot id only if the action rule is configured in a frontend. The point is that at configuration parsing time, it is impossible to check which frontend could point to this backend (furthermore if we use dynamic backend name resolution at runtime). The documentation has been updated to warn the user to ensure that relevant frontends have required declaration when such rule has to be used in a backend. If no capture slot can be found, then the action will just not be executed and HAProxy will process the next one in the list, as expected. This should be backported to all supported branches (bug created as part of a bug fix introduced into 1.7 and backported to 1.6).
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)