mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-11-28 22:31:06 +01:00
Code Issues Projects Releases Wiki Activity

DOC: config: use the word 'backend' instead of 'proxy' in 'track' description

Browse Source 
User @nwehrman reported in issue #2328 that the used of "proxy" instead
of "backend" in the argument of the "track" server keyword is confusing.
Admittedly, all other places in the doc use "backend/server" instead of
"proxy/server", so let's update it for the sake of consistency.
This commit is contained in:
Willy Tarreau 2023-11-10 16:26:32 +01:00
parent 150c0da889
commit 9530e7dcd3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/configuration.txt
View File

@ -16952,11 +16952,11 @@ tfo
"empty-response" and "response-timeout" keywords for "retry-on", or HAProxy "empty-response" and "response-timeout" keywords for "retry-on", or HAProxy
won't be able to retry the connection on failure. See also "no-tfo". won't be able to retry the connection on failure. See also "no-tfo".
track [<proxy>/]<server> track [<backend>/]<server>
This option enables ability to set the current state of the server by tracking This option enables ability to set the current state of the server by tracking
another one. It is possible to track a server which itself tracks another another one. It is possible to track a server which itself tracks another
server, provided that at the end of the chain, a server has health checks server, provided that at the end of the chain, a server has health checks
enabled. If <proxy> is omitted the current one is used. If disable-on-404 is enabled. If <backend> is omitted the current one is used. If disable-on-404 is
used, it has to be enabled on both proxies. used, it has to be enabled on both proxies.
tls-tickets tls-tickets