c79c7f4912
These both functions are buggy and don't respect the documentation. They must wait for more data, if possible. For Channel.data(), it must happen if not enough data was received orf if no length was specified and no data was received. The first case is properly handled but not the second one. An empty string is return instead. In addition, if there is no data and the channel can't receive more data, 'nil' value must be returned. In the same spirit, for Channel.line(), we must try to wait for more data when no line is found if not enough data was received or if no length was specified. Here again, only the first case is properly handled. And for this function too, 'nil' value must be returned if there is no data and the channel can't receive more data. This patch is related to the issue #1993. It must be backported as far as 2.5. (cherry picked from commit 0ae2e63d85d1da9c20b2a8b511cd8ced8558e769) Signed-off-by: Willy Tarreau <w@1wt.eu> (cherry picked from commit 08554a4669b92f4d6c988a7dd4fd318c9e8ec903) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
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)