9e8ea0ae6f
Historically some messages used to already contain the trailing LF but not all, and __do_send_log adds a new one in needed cases. It also does trim a trailing LF in certain cases while computing the max message length, as a result of subtracting 1 to the available room in the destination buffer. But the way it's done is wrong since some messages still contain it. So the code was fixed to always trim the trailing LF from messages if present, and then only subtract 1 from the destination buffer room instead of the size.. Note: new sink API is not designed to receive a trailing LF on event messages This could be backported to relevant stable versions with particular care since the logic of the code changed a bit since 1.6 and there may be other locations that need to be adjusted.
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)