Docs: clarify retry_on_error situations

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 68ffda378c0d6b084501a04550c02b147f54c99b..f3679a390fa6ece7fcc9dce143ad36a46089eab5 100644 (file)
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -7381,10 +7381,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