mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-05 09:21:42 +01:00
600985df41
For now, these buffers are allocated when the httpclient is created and freed when it is released. Usually, we try to avoid to keep buffer allocated if it is not required. Empty buffers should be released ASAP. Apart for that, there is no issue with the response side because a copy is always performed. However, for the request side, a swap with the channel's buffer is always performed. And there is no guarantee the channel's buffer is allocated. Thus, after the swap, the httpclient can retrieve a null buffer. In practice, this never happens. But this may change. And it will be required for a futur fix. So, now, we systematically take care to have an allocated buffer when we want to write in it. And it is released as soon as it becomes empty. This patch should be backported to 2.5.
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)