DOC: config: fix confusing init-state examples

in 50322dff ("MEDIUM: server: add init-state"), some examples on how to
use init-state server keyword were added alongside with the keyword
documentation.

However, as reported by Nick Ramirez, there was an error because the
example that stated that haproxy will pass the traffic to the server after
3 successful health checks used the "init-state down" instead of the
"init-state fully-down". Thus the behavior wouldn't match what the
comment said (only 1 successful health check was required).

Here we fix the example in itself to match with the comment. Also the
following example ("# or") was also affected, but it is kind of
redundant as the main purpose of the examples are to illustrate the
feature in itself and not how to use server-template directive, so we
remove it.

This should be backported in 3.1 with 50322dff

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 684a7a80e5ff90cb13e3cdaf4a4df3508cd8c68d..aab1898f7410ad62f762aeadd95112acec39ba1c 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -18143,13 +18143,8 @@ init-state { fully-up | up | down | fully-down }
       # pass traffic to the server only after 3 successful health checks
       backend google-backend
         mode http
-        server srv1 google.com:80 check init-state down rise 3
-        server srv2 google.com:80 check init-state down rise 3
-
-      # or
-      listen
-        mode http
-        server-template srv 2 google.com:80 check init-state down rise 3
+        server srv1 google.com:80 check init-state fully-down rise 3
+        server srv2 google.com:80 check init-state fully-down rise 3
 
 See also: "option tcp-check", "option httpchk"