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.
This commit is contained in:
Lukas Tribus 2022-03-26 20:43:48 +01:00 committed by Willy Tarreau
parent 0541c2b978
commit 4646e9c9cb

View File

@ -13034,8 +13034,6 @@ timeout client <timeout>
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".
@ -13130,10 +13128,6 @@ timeout http-keep-alive <timeout>
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".