From ea9c4a3a923e88ab12cc08e36b8da9136e236da7 Mon Sep 17 00:00:00 2001 From: Amos Jeffries Date: Fri, 16 Sep 2011 05:06:32 -0600 Subject: [PATCH] Docs: clarify retry_on_error situations --- src/cf.data.pre | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/src/cf.data.pre b/src/cf.data.pre index f7211f9a32..5377fc9c3a 100644 --- a/src/cf.data.pre +++ b/src/cf.data.pre @@ -6682,10 +6682,16 @@ TYPE: onoff LOC: Config.retry.onerror DEFAULT: off DOC_START - If set to on Squid will automatically retry requests when - receiving an error response. This is mainly useful if you - are in a complex cache hierarchy to work around access - control errors. + If set to ON Squid will automatically retry requests when + receiving an error response with status 403 (Forbidden), + 500 (Internal Error), 501 or 503 (Service not available). + Status 502 and 504 (Gateway errors) are always retried. + + This is mainly useful if you are in a complex cache hierarchy to + work around access control errors. + + NOTE: This retry will attempt to find another working destination. + Which is different from the server which just failed. DOC_END NAME: as_whois_server -- 2.47.2