DOC: reflect H2 timeout changes
Reverts 75df9d7a7 ("DOC: explain HTTP2 timeout behavior") since H2
connections now respect "timeout http-keep-alive".
If commit 15a4733d5d ("BUG/MEDIUM: mux-h2: make use of http-request
and keep-alive timeouts") is backported, this DOC change needs to
be backported along with it.
(cherry picked from commit 4646e9c9cbc04a413b9a84e2bfcab3b119e9f21b)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit c3ed25931391b38e34e5579ead5172f487bd72fe)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
diff --git a/doc/configuration.txt b/doc/configuration.txt
index d844a1a..dbe23f0 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -12812,8 +12812,6 @@
during startup because it may result in accumulation of expired sessions in
the system if the system's timeouts are not configured either.
- This also applies to HTTP/2 connections, which will be closed with GOAWAY.
-
See also : "timeout server", "timeout tunnel", "timeout http-request".
@@ -12908,10 +12906,6 @@
set in the frontend to take effect, unless the frontend is in TCP mode, in
which case the HTTP backend's timeout will be used.
- When using HTTP/2 "timeout client" is applied instead. This is so we can keep
- using short keep-alive timeouts in HTTP/1.1 while using longer ones in HTTP/2
- (where we only have one connection per client and a connection setup).
-
See also : "timeout http-request", "timeout client".