From: Willy Tarreau Date: Fri, 10 Nov 2023 15:26:32 +0000 (+0100) Subject: DOC: config: use the word 'backend' instead of 'proxy' in 'track' description X-Git-Tag: v2.9-dev10~101 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9530e7dcd38f2a771558c75b40c7decf14c1bc7a;p=thirdparty%2Fhaproxy.git DOC: config: use the word 'backend' instead of 'proxy' in 'track' description 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. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 7b3364f92d..d46905bee8 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -16952,11 +16952,11 @@ tfo "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". -track [/] +track [/] 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 server, provided that at the end of the chain, a server has health checks - enabled. If is omitted the current one is used. If disable-on-404 is + enabled. If is omitted the current one is used. If disable-on-404 is used, it has to be enabled on both proxies. tls-tickets