mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-12 14:35:14 +00:00
a254a37ad7
When running in HTX mode, if we sent the request, but failed to get the answer, either because the server just closed its socket, we hit a server timeout, or we get a 404, 408, 425, 500, 501, 502, 503 or 504 error, attempt to retry the request, exactly as if we just failed to connect to the server. To do so, add a new backend keyword, "retry-on". It accepts a list of keywords, which can be "none" (never retry), "conn-failure" (we failed to connect, or to do the SSL handshake), "empty-response" (the server closed the connection without answering), "response-timeout" (we timed out while waiting for the server response), or "404", "408", "425", "500", "501", "502", "503" and "504". The default is "conn-failure". |
||
---|---|---|
.. | ||
acl.txt | ||
body-parsing.txt | ||
buffer-api.txt | ||
connect-status.txt | ||
connection-header.txt | ||
connection-scale.txt | ||
entities-v2.txt | ||
entities.fig | ||
entities.pdf | ||
entities.svg | ||
entities.txt | ||
filters.txt | ||
hashing.txt | ||
header-parser-speed.txt | ||
header-tree.txt | ||
http-cookies.txt | ||
http-docs.txt | ||
http-parsing.txt | ||
list.fig | ||
lua_socket.fig | ||
lua_socket.pdf | ||
naming.txt | ||
notes-layers.txt | ||
pattern.dia | ||
pattern.pdf | ||
polling-states.fig | ||
repartition-be-fe-fi.txt | ||
sequence.fig | ||
stats-v2.txt | ||
stream-sock-states.fig |