22<html lang="en">
33 <head>
44 <meta charset="utf-8" />
5- <title>HAProxy version 3.4-dev7-110 - Configuration Manual</title>
5+ <title>HAProxy version 3.4-dev7-147 - Configuration Manual</title>
66 <link href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css" rel="stylesheet" />
77 <link href="https://raw.githubusercontent.com/thomaspark/bootswatch/v3.3.7/cerulean/bootstrap.min.css" rel="stylesheet" />
88 <link href="../css/page.css?0.4.2-15" rel="stylesheet" />
48844884 You can use <strong>left</strong> and <strong>right</strong> arrow keys to navigate between chapters.<br>
48854885 </p>
48864886 <p class="text-right">
4887- <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2026/04/01 </b></small>
4887+ <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2026/04/02 </b></small>
48884888 </p>
48894889 </div>
48904890 <!-- /.sidebar -->
48954895 <div class="text-center">
48964896 <h1><a href="http://www.haproxy.org/" title="HAProxy"><img src="../img/HAProxyCommunityEdition_60px.png?0.4.2-15" /></a></h1>
48974897 <h2>Configuration Manual</h2>
4898- <p><strong>version 3.4-dev7-110 </strong></p>
4898+ <p><strong>version 3.4-dev7-147 </strong></p>
48994899 <p>
49004900 2026/03/20<br>
49014901
@@ -22294,6 +22294,7 @@ <h2 id="chapter-5.1" data-target="5.1"><small><a class="small" href="#5.1">5.1.<
2229422294a bind line :
2229522295
2229622296 quic : mode=HTTP side=FE|BE mux=QUIC flags=HTX|NO_UPG|FRAMED
22297+ qmux : mode=HTTP side=FE|BE mux=QMUX flags=HTX|NO_UPG
2229722298 h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|HOL_RISK|NO_UPG
2229822299 h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
2229922300 none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
@@ -22306,6 +22307,10 @@ <h2 id="chapter-5.1" data-target="5.1"><small><a class="small" href="#5.1">5.1.<
2230622307If the ALPN or the NPN settings are configured, the specified protocols
2230722308should be compatible with the multiplexer's protocol to avoid any issue. For
2230822309instance, if "proto h1" is set, the ALPN should not be set to "h2".
22310+
22311+ QMux is a subset of QUIC which runs over TCP. It corresponds to the following
22312+ draft protocol https://www.ietf.org/archive/id/draft-opik-quic-qmux-01.html.
22313+ It is considered experimental in haproxy for now.
2230922314</pre><a class="anchor" name="quic-cc-algo"></a><a class="anchor" name="5-quic-cc-algo"></a><a class="anchor" name="5.1-quic-cc-algo"></a><a class="anchor" name="quic-cc-algo (Bind and server options)"></a><a class="anchor" name="quic-cc-algo (Bind options)"></a><div class="keyword"><b><a class="anchor" name="quic-cc-algo"></a><a href="#5.1-quic-cc-algo">quic-cc-algo</a></b> <span style="color: #800">{ cubic | newreno | bbr | nocc }</span><span style="color: #008">[(<span style="color: #080"><args,...></span>)]</span></div><pre class="text">This is a QUIC specific setting to select the congestion control algorithm
2231022315for any connection attempts to the configured QUIC listeners. They are
2231122316similar to those used by TCP.
@@ -23638,6 +23643,7 @@ <h2 id="chapter-5.2" data-target="5.2"><small><a class="small" href="#5.2">5.2.<
2363823643a server line :
2363923644
2364023645 quic : mode=HTTP side=FE|BE mux=QUIC flags=HTX|NO_UPG|FRAMED
23646+ qmux : mode=HTTP side=FE|BE mux=QMUX flags=HTX|NO_UPG
2364123647 h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|HOL_RISK|NO_UPG
2364223648 fcgi : mode=HTTP side=BE mux=FCGI flags=HTX|HOL_RISK|NO_UPG
2364323649 h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
@@ -23652,6 +23658,10 @@ <h2 id="chapter-5.2" data-target="5.2"><small><a class="small" href="#5.2">5.2.<
2365223658instance, if "proto h1" is set, the ALPN should not be set to "h2".
2365323659
2365423660See also "<a href="#ws">ws</a>" to use an alternative protocol for websocket streams.
23661+
23662+ QMux is a subset of QUIC which runs over TCP. It corresponds to the following
23663+ draft protocol https://www.ietf.org/archive/id/draft-opik-quic-qmux-01.html.
23664+ It is considered experimental in haproxy for now.
2365523665</pre><a class="anchor" name="quic-cc-algo"></a><a class="anchor" name="5-quic-cc-algo"></a><a class="anchor" name="5.2-quic-cc-algo"></a><a class="anchor" name="quic-cc-algo (Bind and server options)"></a><a class="anchor" name="quic-cc-algo (Server and default-server options)"></a><div class="keyword"><b><a class="anchor" name="quic-cc-algo"></a><a href="#5.2-quic-cc-algo">quic-cc-algo</a></b> <span style="color: #800">{ cubic | newreno | bbr | nocc }</span><span style="color: #008">[(<span style="color: #080"><args,...></span>)]</span></div><pre class="text">This is a QUIC specific setting to select the congestion control algorithm
2365623666for any connection targeting this server. They are similar to those used by
2365723667TCP. See the bind option with a similar name for a complete description of
@@ -35008,14 +35018,19 @@ <h2 id="chapter-12.8" data-target="12.8"><small><a class="small" href="#12.8">12
3500835018 option is independent of the CLI command, so no human intervention
3500935019 is required.
3501035020
35021+ delay - apply an initial wait of "<a href="#dns-delay">dns-delay</a>" before proceeding. Without
35022+ "dns", the challenge is submitted after the delay expires. When
35023+ combined with "dns", the initial wait is applied before starting
35024+ the DNS pre-checks.
35025+
3501135026 none - no readiness condition; the challenge is submitted to the ACME
3501235027 server immediately without waiting for any external confirmation.
3501335028 This option cannot be combined with others.
3501435029
35015- Multiple values can be combined with a comma so that both conditions must be
35016- met. The order of the values is not significant. When "cli" and "dns" are
35017- combined, HAProxy first waits for the CLI confirmation before triggering the
35018- DNS propagation check .
35030+ Multiple values can be combined with a comma. When several conditions are
35031+ specified, HAProxy processes them in the following order: first it waits for
35032+ the CLI confirmation ("cli"), then applies the initial delay ("delay"), then
35033+ performs the DNS pre-checks ("dns") .
3501935034
3502035035This option is only compatible with the dns-01 challenge type.
3502135036
@@ -35036,9 +35051,20 @@ <h2 id="chapter-12.8" data-target="12.8"><small><a class="small" href="#12.8">12
3503635051<pre class="prettyprint">
3503735052<code>directory https://acme-staging-v02.api.letsencrypt.org/directory
3503835053</code></pre>
35039- </div><a class="anchor" name="dns-delay"></a><a class="anchor" name="12-dns-delay"></a><a class="anchor" name="12.8-dns-delay"></a><a class="anchor" name="dns-delay (Other sections)"></a><a class="anchor" name="dns-delay (ACME)"></a><div class="keyword"><b><a class="anchor" name="dns-delay"></a><a href="#12.8-dns-delay">dns-delay</a></b> <span style="color: #080"><time></span></div><pre class="text">When "<a href="#challenge-ready">challenge-ready</a>" includes "dns", configure the delay before the first
35040- DNS resolution attempt and between retries. The value is a time expressed in
35041- HAProxy time format (e.g. "5m", "300s"). Default is 300 seconds.
35054+ </div><a class="anchor" name="dns-delay"></a><a class="anchor" name="12-dns-delay"></a><a class="anchor" name="12.8-dns-delay"></a><a class="anchor" name="dns-delay (Other sections)"></a><a class="anchor" name="dns-delay (ACME)"></a><div class="keyword"><b><a class="anchor" name="dns-delay"></a><a href="#12.8-dns-delay">dns-delay</a></b> <span style="color: #080"><time></span></div><pre class="text">Configure the delay used by "<a href="#challenge-ready">challenge-ready</a>" conditions "delay" and "dns".
35055+ The value is a time expressed in HAProxy time format (e.g. "5m", "300s").
35056+ Default is 30 seconds.
35057+
35058+ Its role depends on the "<a href="#challenge-ready">challenge-ready</a>" conditions in use:
35059+
35060+ delay - the challenge is submitted after this delay expires, without
35061+ any DNS pre-check.
35062+
35063+ dns - the delay between two consecutive DNS resolution attempts.
35064+ The first probe fires immediately without any initial wait.
35065+
35066+ dns+delay - the initial wait before the first DNS resolution attempt, and
35067+ the delay between subsequent retries.
3504235068
3504335069Note that the resolution goes through the configured "default" resolvers
3504435070section, not the authoritative name servers. Results may therefore still be
@@ -35048,9 +35074,11 @@ <h2 id="chapter-12.8" data-target="12.8"><small><a class="small" href="#12.8">12
3504835074is a time expressed in HAProxy time format (e.g. "10m", "600s"). Default is
3504935075600 seconds.
3505035076
35051- If the next DNS resolution attempt would be triggered after the timeout has
35052- elapsed (taking into account "<a href="#dns-delay">dns-delay</a>"), the challenge is aborted with an
35053- error. This prevents an infinite retry loop when DNS propagation fails.
35077+ The timer starts from the moment the first DNS resolution attempt is
35078+ triggered (after the initial "<a href="#dns-delay">dns-delay</a>"). If the next resolution attempt
35079+ would be triggered after the timeout has elapsed, the challenge is aborted
35080+ with an error. This prevents an infinite retry loop when DNS propagation
35081+ fails.
3505435082</pre><div class="page-header"><b>See also:</b> "<a href="#dns-delay">dns-delay</a>"</div>
3505535083<a class="anchor" name="keytype"></a><a class="anchor" name="12-keytype"></a><a class="anchor" name="12.8-keytype"></a><a class="anchor" name="keytype (Other sections)"></a><a class="anchor" name="keytype (ACME)"></a><div class="keyword"><b><a class="anchor" name="keytype"></a><a href="#12.8-keytype">keytype</a></b> <span style="color: #080"><string></span></div><pre class="text">Configure the type of key that will be generated. Value can be either "RSA"
3505635084or "ECDSA". You can also configure the "<span class="dropdown"><a class="dropdown-toggle" data-toggle="dropdown" href="#">curves<span class="caret"></span></a><ul class="dropdown-menu"><li class="dropdown-header">This keyword is available in sections :</li><li><a href="#curves%20%28Load%20options%29">Load options</a></li><li><a href="#curves%20%28ACME%29">ACME</a></li><li><a href="#curves%20%28Bind%20options%29">Bind options</a></li><li><a href="#curves%20%28Server%20and%20default-server%20options%29">Server and default-server options</a></li></ul></span>" for ECDSA and the number of
@@ -35156,7 +35184,7 @@ <h2 id="chapter-12.9" data-target="12.9"><small><a class="small" href="#12.9">12
3515635184 <br>
3515735185 <hr>
3515835186 <div class="text-right">
35159- HAProxy 3.4-dev7-110 – Configuration Manual<br>
35187+ HAProxy 3.4-dev7-147 – Configuration Manual<br>
3516035188 <small>, 2026/03/20</small>
3516135189 </div>
3516235190 </div>
0 commit comments