DOC: option redispatch should mention persist options

"option redispatch" remains vague in which cases a session would persist;
let's mention "option persist" and "force-persist" as an example so folks
don't draw the conclusion that this may be default.

Should be backported to stable branches.

(cherry picked from commit 5926fb78233ab4ba95b07db3815ee62f5cbc5082)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit 6d1a374721b2813a2ad61bf0e88e0e58a2a0c8b0)
Signed-off-by: Willy Tarreau <w@1wt.eu>

diff --git a/doc/configuration.txt b/doc/configuration.txt
index cac0852..32efaf7 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -10326,7 +10326,8 @@ no option redispatch
 
 
   In HTTP mode, if a server designated by a cookie is down, clients may
-  definitely stick to it because they cannot flush the cookie, so they will not
+  definitely stick to it, for example when using "option persist" or
+  "force-persist", because they cannot flush the cookie, so they will not
   be able to access the service anymore.
 
   Specifying "option redispatch" will allow the proxy to break cookie or
@@ -10359,7 +10360,7 @@ no option redispatch
   If this option has been enabled in a "defaults" section, it can be disabled
   in a specific instance by prepending the "no" keyword before it.
 
-  See also : "retries", "force-persist"
+  See also : "option persist", "force-persist", "retries"
 
 
 option redis-check