Hi
please find the patch attached.
This email address is not subscribed to the list, please keep it in Cc
when replying.
Best regards
Tim Düsterhus
Developer WoltLab GmbH
--
WoltLab GmbH
Nedlitzer Str. 27B
14469 Potsdam
Tel.: +49 331 96784338
duester...@woltlab.com
www.woltlab.com
Managing director:
Marcel Werk
AG Potsdam HRB 26795 P
From 2ad862b7a5df3b19152d226d62d6a4753529a719 Mon Sep 17 00:00:00 2001
From: Tim Duesterhus <duester...@woltlab.com>
Date: Tue, 13 Jun 2023 15:15:47 +0200
Subject: [PATCH] DOC: Attempt to fix dconv parsing error for
tune.h2.fe.initial-window-size
To: haproxy@formilux.org
It appears that dconv dislikes the "see also" part being on the same line as
the regular paragraph. The beginning of the line does not show up in the
rendered version.
Attempt to fix this by inserting an additional newline which is consistent with
other options.
---
doc/configuration.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/configuration.txt b/doc/configuration.txt
index c17e5e3da..33728a202 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -2960,6 +2960,7 @@ tune.h2.be.initial-window-size <number>
It can make sense to slightly increase this value to allow faster downloads
or to reduce CPU usage on the servers, at the expense of creating unfairness
between clients. It doesn't affect resource usage.
+
See also: tune.h2.initial-window-size.
tune.h2.be.max-concurrent-streams <number>
@@ -2986,7 +2987,9 @@ tune.h2.fe.initial-window-size <number>
bandwidth per client over a 100 ms ping time, and 500 Mbps for 1 ms ping
time. It doesn't affect resource usage. Using too large values may cause
clients to experience a lack of responsiveness if pages are accessed in
- parallel to large uploads. See also: tune.h2.initial-window-size.
+ parallel to large uploads.
+
+ See also: tune.h2.initial-window-size.
tune.h2.fe.max-concurrent-streams <number>
Sets the HTTP/2 maximum number of concurrent streams per incoming connection
--
2.40.1
