mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-30 14:31:08 +01:00
4c52e4b560
@davidmogar reported a github issue (#227) about problems with do-resolve action when the request contains a body. The variable was never populated in such case, despite tcpdump shows a valid DNS response coming back. The do-resolve action is a task in HAProxy and so it's waken by the scheduler each time the scheduler think such task may have some work to do. When a simple HTTP request is sent, then the task is called, it sends the DNS request, then the scheduler will wake up the task again later once the DNS response is there. Now, when the client send a PUT or a POST request (or any other type) with a BODY, then the do-resolve action if first waken up once the headers are processed. It sends the DNS request. Then, when the bytes for the body are processed by HAProxy AND the DNS response has not yet been received, then the action simply terminates and cleans up all the data associated to this resolution... This patch detect such behavior and if the action is now waken up while a DNS resolution is in RUNNING state, then the action will tell the scheduler to wake it up again later. Backport status: 2.0 and above
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)