From: Amaury Denoyelle Date: Wed, 14 Aug 2024 16:00:20 +0000 (+0200) Subject: DOC: quic: document nocc debug congestion algorithm X-Git-Tag: v3.1-dev6~31 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5b6e8c4d4dc38e16b28c9980344a83ebbbc6bbbb;p=thirdparty%2Fhaproxy.git DOC: quic: document nocc debug congestion algorithm Document nocc congestion algorithm as an entry of quic-cc-algo. Highlight the fact that it is reserved for debugging and should not be used outside of this use case. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 16ba51ce34..b2ea8dfda4 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -16660,8 +16660,8 @@ proto instance, it is possible to force the http/2 on clear TCP by specifying "proto h2" on the bind line. -quic-cc-algo { cubic | newreno } -quic-cc-algo { cubic | newreno }(max_window) +quic-cc-algo { cubic | newreno | nocc } +quic-cc-algo { cubic | newreno | nocc }(max_window) This is a QUIC specific setting to select the congestion control algorithm for any connection attempts to the configured QUIC listeners. They are similar to those used by TCP. An optional value in bytes may be used to specify the @@ -16676,6 +16676,11 @@ quic-cc-algo { cubic | newreno }(max_window) # cubic congestion control algorithm with one megabytes as window quic-cc-algo cubic(1m) + A special value "nocc" may be used to force a fixed congestion window always + set at the maximum size. It is reserved for debugging scenarios to remove any + side effects caused by the congestion controller. It must not be used in + production as it can quickly lead to network issues such as a high loss rate. + quic-force-retry This is a QUIC specific setting which forces the use of the QUIC Retry feature for all the connection attempts to the configured QUIC listeners. It consists