Hi

On 4/14/23 18:42, William Dauchy wrote:
Thank you for your patch.
Do you think you could come back with a patch which is only modifying
the section you want? It seems you did a change on the full file
instead which makes the review quite hard.


It appears they changed the line endings of the entire file. Appending ?w=1 to the PR shows a useful diff. I've attached a fixed patch.

Best regards
Tim Düsterhus
From cc26527ca0afab9384e572bbf351e3965d8f25f8 Mon Sep 17 00:00:00 2001
From: Craig <99729+cr...@users.noreply.github.com>
Date: Fri, 14 Apr 2023 17:29:04 +0200
Subject: [PATCH] Improve wording of http-request wait-for-body

Improve wording of http-request wait-for-body so it's easier to understand.
---
 doc/configuration.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 3adab3487..e0e5f571c 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -7839,11 +7839,11 @@ http-request wait-for-body time <time> [ at-least <bytes> ]
              [ { if | unless } <condition> ]
 
   This will delay the processing of the request waiting for the payload for at
-  most <time> milliseconds. if "at-least" argument is specified, HAProxy stops
-  to wait the payload when the first <bytes> bytes are received. 0 means no
-  limit, it is the default value. Regardless the "at-least" argument value,
+  most <time> milliseconds. If the "at-least" argument is specified, HAProxy
+  stops to wait when the first <bytes> payload bytes are received. 0 means no
+  limit, which is the default value. Regardless of the "at-least" argument value,
   HAProxy stops to wait if the whole payload is received or if the request
-  buffer is full.  This action may be used as a replacement to "option
+  buffer is full. This action may be used as a replacement to "option
   http-buffer-request".
 
   Arguments :
-- 
2.40.0

Reply via email to