mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-17 06:41:00 +01:00
52cc45dfa5
As noticed in this thread, some bogus configurations are not always easy to spot: https://www.mail-archive.com/haproxy@formilux.org/msg44558.html Here it was about config keywords being used in ACL patterns where strings were expected, hence they're always valid. Since we have the diag mode (-dD) we can perform some extra checks when it's used, and emit them to suggest the user there might be an issue. Here we detect a few common words (logic such as "and"/"or"/"||" etc), C++/JS comments mistakenly used to try to isolate final args, and words that have the exact name of a sample fetch or an ACL keyword. These checks are only done in diag mode of course.
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)