|
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="utf-8" /> |
5 | | - <title>HAProxy version 3.2.19 - Configuration Manual</title> |
| 5 | + <title>HAProxy version 3.2.19-29 - Configuration Manual</title> |
6 | 6 | <link href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css" rel="stylesheet" /> |
7 | 7 | <link href="https://raw.githubusercontent.com/thomaspark/bootswatch/v3.3.7/cerulean/bootstrap.min.css" rel="stylesheet" /> |
8 | 8 | <link href="../css/page.css?0.4.2-15" rel="stylesheet" /> |
|
4636 | 4636 | You can use <strong>left</strong> and <strong>right</strong> arrow keys to navigate between chapters.<br> |
4637 | 4637 | </p> |
4638 | 4638 | <p class="text-right"> |
4639 | | - <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2026/05/11</b></small> |
| 4639 | + <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2026/05/21</b></small> |
4640 | 4640 | </p> |
4641 | 4641 | </div> |
4642 | 4642 | <!-- /.sidebar --> |
|
4647 | 4647 | <div class="text-center"> |
4648 | 4648 | <h1><a href="http://www.haproxy.org/" title="HAProxy"><img src="../img/HAProxyCommunityEdition_60px.png?0.4.2-15" /></a></h1> |
4649 | 4649 | <h2>Configuration Manual</h2> |
4650 | | - <p><strong>version 3.2.19</strong></p> |
| 4650 | + <p><strong>version 3.2.19-29</strong></p> |
4651 | 4651 | <p> |
4652 | 4652 | 2026/05/11<br> |
4653 | 4653 |
|
@@ -12615,7 +12615,10 @@ <h2 id="chapter-4.2" data-target="4.2"><small><a class="small" href="#4.2">4.2.< |
12615 | 12615 |
|
12616 | 12616 | none don't hash the key, the key will be used as a hash, this can be |
12617 | 12617 | useful to manually hash the key using a converter for that purpose |
12618 | | - and let haproxy use the result directly. |
| 12618 | + and let haproxy use the result directly. The operation will |
| 12619 | + convert the key to a string if it is not already, and parse it as |
| 12620 | + an integer whose value will be used as the key. Some input key |
| 12621 | + types might not be relevant here (e.g. IP addresses). |
12619 | 12622 |
|
12620 | 12623 | <modifier> indicates an optional method applied after hashing the key : |
12621 | 12624 |
|
@@ -22224,27 +22227,32 @@ <h2 id="chapter-5.2" data-target="5.2"><small><a class="small" href="#5.2">5.2.< |
22224 | 22227 | effect to extend the effective check interval. In such a case, reducing the |
22225 | 22228 | "<a href="#inter">inter</a>" setting will have a very limited effect as it will not be able to |
22226 | 22229 | reduce the time spent in the queue. |
22227 | | -</pre><a class="anchor" name="init-state"></a><a class="anchor" name="5-init-state"></a><a class="anchor" name="5.2-init-state"></a><a class="anchor" name="init-state (Bind and server options)"></a><a class="anchor" name="init-state (Server and default-server options)"></a><div class="keyword"><b><a class="anchor" name="init-state"></a><a href="#5.2-init-state">init-state</a></b> <span style="color: #800">{ fully-up | up | down | fully-down }</span></div><pre class="text">May be used in the following contexts: tcp, http |
| 22230 | +</pre><a class="anchor" name="init-state"></a><a class="anchor" name="5-init-state"></a><a class="anchor" name="5.2-init-state"></a><a class="anchor" name="init-state (Bind and server options)"></a><a class="anchor" name="init-state (Server and default-server options)"></a><div class="keyword"><b><a class="anchor" name="init-state"></a><a href="#5.2-init-state">init-state</a></b> <span style="color: #800">{ fully-up | up | down | fully-down | none }</span></div><pre class="text">May be used in the following contexts: tcp, http |
22228 | 22231 | </pre><div><p> May be used in sections :</p><table class="table table-bordered" border="0" cellspacing="0" cellpadding="0"> |
22229 | 22232 | <thead><tr><th>defaults</th><th>frontend</th><th>listen</th><th>backend</th></tr></thead> |
22230 | 22233 | <tr><td class="alert-error pagination-centered">no<br /><img src="../css/cross.png" alt="no" title="no" /></td><td class="alert-error pagination-centered">no<br /><img src="../css/cross.png" alt="no" title="no" /></td><td class="alert-success pagination-centered">yes<br /><img src="../css/check.png" alt="yes" title="yes" /></td><td class="alert-success pagination-centered">yes<br /><img src="../css/check.png" alt="yes" title="yes" /></td></tr> |
22231 | 22234 | </table></div> |
22232 | 22235 | <pre class="text">The "<a href="#init-state">init-state</a>" option sets the initial state of the server: |
22233 | 22236 | - when set to 'fully-up', the server is considered immediately available |
22234 | | - and can turn to the DOWN state when ALL health checks fail. |
22235 | | - - when set to 'up' (the default), the server is considered immediately |
22236 | | - available and will initiate a health check that can turn it to the DOWN |
22237 | | - state immediately if it fails. |
22238 | | - - when set to 'down', the server initially is considered unavailable and |
22239 | | - will initiate a health check that can turn it to the UP state immediately |
22240 | | - if it succeeds. |
| 22237 | + and, if health checks are enabled for this server, it will be turned to |
| 22238 | + the DOWN state when ALL health checks fail. |
| 22239 | + - when set to 'up', the server is considered immediately available and, if |
| 22240 | + health checks are enabled for this server, it will be turned to the DOWN |
| 22241 | + state immediately if the next health check fails. |
| 22242 | + - when set to 'down', the server initially is considered unavailable and, |
| 22243 | + if health checks are enabled for this server, it can be turned to the UP |
| 22244 | + state if the next health check succeeds. |
22241 | 22245 | - when set to 'fully-down', the server is initially considered unavailable |
22242 | | - and can turn to the UP state when ALL health checks succeed. |
| 22246 | + and, if health checks are enabled for this server, it will turned to the |
| 22247 | + UP state when ALL health checks succeed. |
| 22248 | + - when set to 'none' (the default value), init-state management is |
| 22249 | + disabled. It can be used to restore the default behavior when this |
| 22250 | + parameter was inherited from a 'default-server' directive. |
22243 | 22251 |
|
22244 | 22252 | The server's init-state is considered when the HAProxy instance is |
22245 | 22253 | (re)started, a new server is detected (for example via service discovery / |
22246 | 22254 | DNS resolution), a dynamic server is inlived, a server exits maintenance, |
22247 | | -etc. |
| 22255 | +etc. This directive cannot be used when the server is tracking another one. |
22248 | 22256 | </pre><div class="separator"> |
22249 | 22257 | <span class="label label-success">Examples:</span> |
22250 | 22258 | <pre class="prettyprint"> |
@@ -23188,7 +23196,11 @@ <h3 id="chapter-5.3.2" data-target="5.3.2"><small><a class="small" href="#5.3.2" |
23188 | 23196 | As a DNS server may not answer all the IPs in one DNS request, HAProxy keeps |
23189 | 23197 | a cache of previous answers, an answer will be considered obsolete after |
23190 | 23198 | <hold obsolete> seconds without the IP returned. |
23191 | | -</pre><a class="anchor" name="resolvers"></a><a class="anchor" name="5-resolvers"></a><a class="anchor" name="5.3.2-resolvers"></a><a class="anchor" name="resolvers (Bind and server options)"></a><a class="anchor" name="resolvers (The resolvers section)"></a><div class="keyword"><b><a class="anchor" name="resolvers"></a><a href="#5.3.2-resolvers">resolvers</a></b> <span style="color: #080"><resolvers id></span></div><pre class="text"> Creates a new name server list labeled <resolvers id> |
| 23199 | +</pre><a class="anchor" name="resolvers"></a><a class="anchor" name="5-resolvers"></a><a class="anchor" name="5.3.2-resolvers"></a><a class="anchor" name="resolvers (Bind and server options)"></a><a class="anchor" name="resolvers (The resolvers section)"></a><div class="keyword"><b><a class="anchor" name="resolvers"></a><a href="#5.3.2-resolvers">resolvers</a></b> <span style="color: #080"><resolvers id></span></div><pre class="text"> Creates a new name server list labeled <resolvers id>. As mentioned above, |
| 23200 | + the special name "default" always exists and will be automatically created if |
| 23201 | + not explicitly declared; this will be the one internal services such as |
| 23202 | + httpclient rely on. Declaring a "default" entry will affect how such services |
| 23203 | + perform their name resolution. |
23192 | 23204 |
|
23193 | 23205 | A resolvers section accept the following parameters: |
23194 | 23206 | </pre><a class="anchor" name="accepted_payload_size"></a><a class="anchor" name="5-accepted_payload_size"></a><a class="anchor" name="5.3.2-accepted_payload_size"></a><a class="anchor" name="accepted_payload_size (Bind and server options)"></a><a class="anchor" name="accepted_payload_size (The resolvers section)"></a><div class="keyword"><b><a class="anchor" name="accepted_payload_size"></a><a href="#5.3.2-accepted_payload_size">accepted_payload_size</a></b> <span style="color: #080"><nb></span></div><pre class="text">Defines the maximum payload size accepted by HAProxy and announced to all the |
@@ -33319,7 +33331,7 @@ <h2 id="chapter-12.9" data-target="12.9"><small><a class="small" href="#12.9">12 |
33319 | 33331 | <br> |
33320 | 33332 | <hr> |
33321 | 33333 | <div class="text-right"> |
33322 | | - HAProxy 3.2.19 – Configuration Manual<br> |
| 33334 | + HAProxy 3.2.19-29 – Configuration Manual<br> |
33323 | 33335 | <small>, 2026/05/11</small> |
33324 | 33336 | </div> |
33325 | 33337 | </div> |
|
0 commit comments