RepoMirrors/haproxy
1
0
Fork 0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2024-12-14 15:34:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

DOC: explain HTTP2 timeout behavior

Browse Source 
Clarifies that in HTTP2 we don't consider "timeout http-keep-alive", but
"timeout client" instead.
This commit is contained in:
Lukas Tribus 2017-11-24 19:05:12 +01:00 committed by Willy Tarreau
parent 49b4453b58
commit 75df9d7a7a
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/configuration.txt
View File

@ -9855,6 +9855,8 @@ timeout clitimeout <timeout> (deprecated)
during startup because it may results in accumulation of expired sessions in
the system if the system's timeouts are not configured either.
This also applies to HTTP2 connections, which will be closed with GOAWAY.
This parameter replaces the old, deprecated "clitimeout". It is recommended
to use it to write new configurations. The form "timeout clitimeout" is
provided only by backwards compatibility but its use is strongly discouraged.
@ -9960,6 +9962,10 @@ 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 HTTP2 "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 HTTP2
(where we only have one connection per client and a connection setup).
See also : "timeout http-request", "timeout client".