|
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | 4 | <meta charset="utf-8" /> |
5 | | - <title>HAProxy version 3.3-dev1-86 - Configuration Manual</title> |
| 5 | + <title>HAProxy version 3.3-dev1-89 - 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" /> |
|
4612 | 4612 | You can use <strong>left</strong> and <strong>right</strong> arrow keys to navigate between chapters.<br> |
4613 | 4613 | </p> |
4614 | 4614 | <p class="text-right"> |
4615 | | - <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2025/06/17</b></small> |
| 4615 | + <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2025/06/23</b></small> |
4616 | 4616 | </p> |
4617 | 4617 | </div> |
4618 | 4618 | <!-- /.sidebar --> |
|
4623 | 4623 | <div class="text-center"> |
4624 | 4624 | <h1><a href="http://www.haproxy.org/" title="HAProxy"><img src="../img/HAProxyCommunityEdition_60px.png?0.4.2-15" /></a></h1> |
4625 | 4625 | <h2>Configuration Manual</h2> |
4626 | | - <p><strong>version 3.3-dev1-86</strong></p> |
| 4626 | + <p><strong>version 3.3-dev1-89</strong></p> |
4627 | 4627 | <p> |
4628 | 4628 | 2025/06/11<br> |
4629 | 4629 |
|
@@ -10543,11 +10543,11 @@ <h2 id="chapter-3.4" data-target="3.4"><small><a class="small" href="#3.4">3.4.< |
10543 | 10543 | '-' (dash), '_' (underscore) , '.' (dot) and ':' (colon). ACL names are |
10544 | 10544 | case-sensitive, which means that "www" and "WWW" are two different proxies. |
10545 | 10545 |
|
10546 | | -Historically, all proxy names could overlap, it just caused troubles in the |
10547 | | -logs. Since the introduction of content switching, it is mandatory that two |
10548 | | -proxies with overlapping capabilities (frontend/backend) have different names. |
10549 | | -However, it is still permitted that a frontend and a backend share the same |
10550 | | -name, as this configuration seems to be commonly encountered. |
| 10546 | +Historically, all proxy names could overlap when certain conditions were met |
| 10547 | +(e.g. when not having the same frontend/backend capabilities), but it used to |
| 10548 | +cause too many problems in the logs as well as confusion on CLI operations, |
| 10549 | +stick-tables naming and stats retrieval. It is now mandatory that two proxies |
| 10550 | +have different names, regardless of their respective capabilities. |
10551 | 10551 |
|
10552 | 10552 | Right now, two major proxy modes are supported : "tcp", also known as layer 4, |
10553 | 10553 | and "http", also known as layer 7. In layer 4 mode, HAProxy simply forwards |
@@ -16460,6 +16460,7 @@ <h2 id="chapter-4.2" data-target="4.2"><small><a class="small" href="#4.2">4.2.< |
16460 | 16460 | <span class="label label-info">Arguments :</span><pre class="prettyprint arguments"><name> is the internal name assigned to this server. This name will |
16461 | 16461 | appear in logs and alerts. If "<a href="#http-send-name-header">http-send-name-header</a>" is |
16462 | 16462 | set, it will be added to the request header sent to the server. |
| 16463 | + This name must be unique within the backend section. |
16463 | 16464 |
|
16464 | 16465 | <address> is the IPv4 or IPv6 address of the server. Alternatively, a |
16465 | 16466 | resolvable hostname is supported, but this name will be resolved |
@@ -33065,7 +33066,7 @@ <h2 id="chapter-12.9" data-target="12.9"><small><a class="small" href="#12.9">12 |
33065 | 33066 | <br> |
33066 | 33067 | <hr> |
33067 | 33068 | <div class="text-right"> |
33068 | | - HAProxy 3.3-dev1-86 – Configuration Manual<br> |
| 33069 | + HAProxy 3.3-dev1-89 – Configuration Manual<br> |
33069 | 33070 | <small>, 2025/06/11</small> |
33070 | 33071 | </div> |
33071 | 33072 | </div> |
|
0 commit comments