mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-11-29 23:01:03 +01:00
Code Issues Projects Releases Wiki Activity

DOC: Update http-buffer-request description to remove the part about chunks

Browse Source 
The limitation on the first chunk for chunked requests was true for the legacy
HTTP mode. But, it does not exist with the HTX. Becaue, the legacy HTTP mode was
removed in 2.1, this limitation does not exist anymore.
This commit is contained in:
Christopher Faulet 2019-11-19 16:27:25 +01:00
parent 145719a722
commit 6db8a2e021
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/configuration.txt
View File

@ -6235,11 +6235,10 @@ no option http-buffer-request
connecting to the server. Another use case consists in taking the routing connecting to the server. Another use case consists in taking the routing
decision based on the request body's contents. This option placed in a decision based on the request body's contents. This option placed in a
frontend or backend forces the HTTP processing to wait until either the whole frontend or backend forces the HTTP processing to wait until either the whole
body is received, or the request buffer is full, or the first chunk is body is received or the request buffer is full. It can have undesired side
complete in case of chunked encoding. It can have undesired side effects with effects with some applications abusing HTTP by expecting unbuffered
some applications abusing HTTP by expecting unbuffered transmissions between transmissions between the frontend and the backend, so this should definitely
the frontend and the backend, so this should definitely not be used by not be used by default.
default.
See also : "option http-no-delay", "timeout http-request" See also : "option http-no-delay", "timeout http-request"