mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 22:31:28 +02:00
f9f4499429
Functions which are called with dummy streams pass it down the traces and that leads to somewhat confusing "h2s=0x1234568(0,IDL)" for example while the nature of the called function makes this stream useless at that place. Better not report a random pointer, especially since it always requires to look at the code before remembering how this should be interpreted. Now what we're doing is that the idle stream only prints "h2s=IDL" which is shorter and doesn't report a pointer, closed stream do not report anything since the stream ID 0 already implies it, and other ones are reported normally. This could be backported to 2.7 and 2.6 as it improves traces legibility.
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)