You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<a class="anchor" name="tune.quic.frontend.stream-data-ratio"></a><a class="anchor" name="3-tune.quic.frontend.stream-data-ratio"></a><a class="anchor" name="3.2-tune.quic.frontend.stream-data-ratio"></a><a class="anchor" name="tune.quic.frontend.stream-data-ratio (Global parameters)"></a><a class="anchor" name="tune.quic.frontend.stream-data-ratio (Performance tuning)"></a><div class="keyword"><b><a class="anchor" name="tune.quic.frontend.stream-data-ratio"></a><a href="#3.2-tune.quic.frontend.stream-data-ratio">tune.quic.frontend.stream-data-ratio</a></b> <span style="color: #080"><0..100, in percent></span></div><pre class="text">This setting allows to configure the hard limit of the number of data bytes
9686
+
<a class="anchor" name="tune.quic.frontend.max-tx-mem"></a><a class="anchor" name="3-tune.quic.frontend.max-tx-mem"></a><a class="anchor" name="3.2-tune.quic.frontend.max-tx-mem"></a><a class="anchor" name="tune.quic.frontend.max-tx-mem (Global parameters)"></a><a class="anchor" name="tune.quic.frontend.max-tx-mem (Performance tuning)"></a><div class="keyword"><b><a class="anchor" name="tune.quic.frontend.max-tx-mem"></a><a href="#3.2-tune.quic.frontend.max-tx-mem">tune.quic.frontend.max-tx-mem</a></b> <span style="color: #080"><size></span></div><pre class="text">Sets the maximum amount of memory usable by QUIC stack at the transport layer
9687
+
for emission. This serves both as a limit of in flight bytes and multiplexer
9688
+
output buffers. Note that to prevent threads contention this limit is not
9689
+
strictly enforced so it can be exceeded on some occasions. Also, each
9690
+
connection will always be able to use a window of at least 2 datagrams, so a
9691
+
proper maxconn should be used in conjunction.
9692
+
</pre><a class="anchor" name="tune.quic.frontend.stream-data-ratio"></a><a class="anchor" name="3-tune.quic.frontend.stream-data-ratio"></a><a class="anchor" name="3.2-tune.quic.frontend.stream-data-ratio"></a><a class="anchor" name="tune.quic.frontend.stream-data-ratio (Global parameters)"></a><a class="anchor" name="tune.quic.frontend.stream-data-ratio (Performance tuning)"></a><div class="keyword"><b><a class="anchor" name="tune.quic.frontend.stream-data-ratio"></a><a href="#3.2-tune.quic.frontend.stream-data-ratio">tune.quic.frontend.stream-data-ratio</a></b> <span style="color: #080"><0..100, in percent></span></div><pre class="text">This setting allows to configure the hard limit of the number of data bytes
9665
9693
in flight over each stream. It is expressed as a percentage relative to
9666
9694
"<a href="#tune.quic.frontend.max-data-size">tune.quic.frontend.max-data-size</a>" setting, with the result rounded up to
of received data. Lower values will significantly increase CPU usage though.
9823
9851
Another use case is to prevent write timeouts with extremely slow clients due
9824
9852
to the kernel waiting for a large part of the buffer to be read before
9825
-
notifying HAProxy again.
9853
+
notifying HAProxy again. See also tune.notsent-lowat.client and
9854
+
tune.notsent-lowat.server for more effective settings to more finely control
9855
+
memory usage and responsiveness on Linux without hurting performance.
9826
9856
</pre><a class="anchor" name="tune.ssl.cachesize"></a><a class="anchor" name="3-tune.ssl.cachesize"></a><a class="anchor" name="3.2-tune.ssl.cachesize"></a><a class="anchor" name="tune.ssl.cachesize (Global parameters)"></a><a class="anchor" name="tune.ssl.cachesize (Performance tuning)"></a><div class="keyword"><b><a class="anchor" name="tune.ssl.cachesize"></a><a href="#3.2-tune.ssl.cachesize">tune.ssl.cachesize</a></b> <span style="color: #080"><number></span></div><pre class="text">Sets the size of the global SSL session cache, in a number of blocks. A block
9827
9857
is large enough to contain an encoded session without peer certificate. An
9828
9858
encoded session with peer certificate is stored in multiple blocks depending
The following keywords are usable in the ACME section:
10923
10953
</pre><a class="anchor" name="account-key"></a><a class="anchor" name="3-account-key"></a><a class="anchor" name="3.13-account-key"></a><a class="anchor" name="account-key (Global parameters)"></a><a class="anchor" name="account-key (ACME)"></a><div class="keyword"><b><a class="anchor" name="account-key"></a><a href="#3.13-account-key">account-key</a></b> <span style="color: #080"><filename></span></div><pre class="text">Configure the path to the account key. The key need to be generated before
10924
10954
launching HAProxy. If no account keyword is used, the acme section will try
10925
-
to load a filename using the section name "<name>.account.key"
10955
+
to load a filename using the section name "<name>.account.key". If the file
10956
+
doesn't exist, HAProxy will generate one, using the parameters from the acme
10957
+
section.
10926
10958
10927
-
You can generate an RSA private key with openssl:
10959
+
You can also generate manually an RSA private key with openssl:
</div><a class="anchor" name="keytype"></a><a class="anchor" name="3-keytype"></a><a class="anchor" name="3.13-keytype"></a><a class="anchor" name="keytype (Global parameters)"></a><a class="anchor" name="keytype (ACME)"></a><div class="keyword"><b><a class="anchor" name="keytype"></a><a href="#3.13-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"
10950
10982
or "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%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
10951
10983
"<a href="#bits">bits</a>" for RSA. By default EC384 keys are generated.
10984
+
</pre><a class="anchor" name="map"></a><a class="anchor" name="3-map"></a><a class="anchor" name="3.13-map"></a><a class="anchor" name="map (Global parameters)"></a><a class="anchor" name="map (ACME)"></a><div class="keyword"><b><a class="anchor" name="map"></a><a href="#3.13-map">map</a></b> <span style="color: #080"><map></span></div><pre class="text">Configure the map which will be used to store token (key) and thumbprint
10985
+
(value), which is useful to reply to a challenge when there are multiple
10986
+
account used. The acme task will add entries before validating the challenge
10987
+
and will remove the entries at the end of the task.
the <default_value>. If the <default_value> is not set, the converter fails
25309
25348
and acts as if no input value could be fetched. If the <match_type> is not
25310
25349
set, it defaults to "<a href="#str">str</a>". Likewise, if the <output_type> is not set, it
25311
-
defaults to "<a href="#str">str</a>". For convenience, the "<a href="#map">map</a>" keyword is an alias for
25350
+
defaults to "<a href="#str">str</a>". For convenience, the "<span class="dropdown"><a class="dropdown-toggle" data-toggle="dropdown" href="#">map<span class="caret"></span></a><ul class="dropdown-menu"><li class="dropdown-header">This keyword is available in sections :</li><li><a href="#map%20%28ACME%29">ACME</a></li><li><a href="#map%20%28Converters%29">Converters</a></li></ul></span>" keyword is an alias for
25312
25351
"map_str" and maps a string to another string. <map_name> must follow the
25313
25352
format described in 2.7. about name format for maps and ACLs
0 commit comments