From 6db8a2e02132d7370284869d5964512534183d45 Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Tue, 19 Nov 2019 16:27:25 +0100 Subject: [PATCH] DOC: Update http-buffer-request description to remove the part about chunks 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. --- doc/configuration.txt | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index b17ab9064..463d17275 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -6235,11 +6235,10 @@ no option http-buffer-request 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 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 - complete in case of chunked encoding. It can have undesired side effects with - some applications abusing HTTP by expecting unbuffered transmissions between - the frontend and the backend, so this should definitely not be used by - default. + body is received or the request buffer is full. It can have undesired side + effects with some applications abusing HTTP by expecting unbuffered + transmissions between the frontend and the backend, so this should definitely + not be used by default. See also : "option http-no-delay", "timeout http-request"