[DOC] documentation for the "retries" parameter was missing.
This commit is contained in:
parent
7c669d7e0f
commit
e5c5ce970f
|
@ -2590,6 +2590,28 @@ reqitarpit <search> (ignore case)
|
||||||
manipulation
|
manipulation
|
||||||
|
|
||||||
|
|
||||||
|
retries <value>
|
||||||
|
Set the number of retries to perform on a server after a connection failure
|
||||||
|
May be used in sections: defaults | frontend | listen | backend
|
||||||
|
yes | no | yes | yes
|
||||||
|
Arguments :
|
||||||
|
<value> is the number of times a connection attempt should be retried on
|
||||||
|
a server when a connection either is refused or times out. The
|
||||||
|
default value is 3.
|
||||||
|
|
||||||
|
It is important to understand that this value applies to the number of
|
||||||
|
connection attempts, not full requests. When a connection has effectively
|
||||||
|
been established to a server, there will be no more retry.
|
||||||
|
|
||||||
|
In order to avoid immediate reconnections to a server which is restarting,
|
||||||
|
a turn-around timer of 1 second is applied before a retry occurs.
|
||||||
|
|
||||||
|
When "option redispatch" is set, the last retry may be performed on another
|
||||||
|
server even if a cookie references a different server.
|
||||||
|
|
||||||
|
See also : "option redispatch"
|
||||||
|
|
||||||
|
|
||||||
rspadd <string>
|
rspadd <string>
|
||||||
Add a header at the end of the HTTP response
|
Add a header at the end of the HTTP response
|
||||||
May be used in sections : defaults | frontend | listen | backend
|
May be used in sections : defaults | frontend | listen | backend
|
||||||
|
|
Loading…
Reference in New Issue