mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-05 09:21:42 +01:00
af9990f035
As the peers protocol expects to parse at least one encoded integer value for each stick-table data field even when not configured on the local side, about the "server_name" data field we must emit something even if it has not been set (no server was configured for instance). As this data field is made of first one encoded integer which is the length of the remaining data (the dictionary cache entry), we encode the length 0 when emitting such an absent dictionary cache entry. On the remote side, when we decode such an integer with 0 as value, we stop parsing the data field and that's it. Must be backported to 2.0.
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)