mirror of
https://github.com/haproxy/haproxy.git
synced 2026-04-20 22:01:49 -04:00
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.
This commit is contained in:
parent
d48b5add88
commit
5926fb7823
1 changed files with 3 additions and 2 deletions
|
|
@ -10875,7 +10875,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
|
||||
|
|
@ -10908,7 +10909,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
|
||||
|
|
|
|||
Loading…
Reference in a new issue