mirror of
http://git.haproxy.org/git/haproxy.git
synced 2026-02-23 18:54:43 +02:00
d0142e7224
When using multiple filters with "show table", it can be useful to report which filter entry failed > show table MY_TABLE data.gpc0 gt 0 data.gpc0a lt 1000 Filter entry #2: Unknown data type > show table MY_TABLE data.gpc0 gt 0 data.gpc0 lt 1000a Filter entry #2: Require a valid integer value to compare against We now also catch garbage data after the filter > show table MY_TABLE data.gpc0 gt 0 data.gpc0 lt 1000 data.gpc0 gt 1\ data.gpc0 gt 10 a Detected extra data in filter, 16th word of input, after '10' Even before multi-filter feature we've also silently accepted garbage after the input, hiding potential bugs > show table MY_TABLE data.gpc0 gt 0 data.gpc0 or > show table MY_TABLE data.gpc0 gt 0 a In both cases, only first filter entry would be used, silently ignoring extra filter entry or garbage data. Last, but not the least, it is now possible to detect multi-filter feature from cli with something like the following: > show table MY_TABLE data.blah Filter entry #1: Unknown data type
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)