From: Amaury Denoyelle <adenoyelle@haproxy.com>
Date: Wed, 14 Oct 2020 16:17:12 +0000 (+0200)
Subject: DOC: Describe reuse safe for HOL handling
X-Git-Tag: v2.3-dev7~33
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2717965387f4f44df923ce988bccc128276341fb;p=thirdparty%2Fhaproxy.git

DOC: Describe reuse safe for HOL handling

Explain the special case of server connections using a protocol subject
to HOL on http-reuse safe mode.
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index e9bde91125..a1a743f0b9 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -6611,7 +6611,12 @@ http-reuse { never | safe | aggressive | always }
                  closes the connection when the request is being sent, the
                  browser can decide to silently retry it. Since it is exactly
                  equivalent to regular keep-alive, there should be no side
-                 effects.
+                 effects. There is also a special handling for the connections
+                 using protocols subject to Head-of-line blocking (backend with
+                 h2 or fcgi). In this case, when at least one stream is
+                 processed, the used connection is reserved to handle streams
+                 of the same session. When no more streams are processed, the
+                 connection is released and can be reused.
 
     - "aggressive" : this mode may be useful in webservices environments where
                  all servers are not necessarily known and where it would be