Squid configuration directive icap_service_failure_limit
Available in: v7 v6 v5 v4 3.5 3.4 3.3 3.2 3.1 3.0
For older versions than v4 see the linked pages above
Configuration Details:
Option Name: | icap_service_failure_limit |
---|---|
Replaces: | |
Requires: | --enable-icap-client |
Default Value: | icap_service_failure_limit 10 |
Suggested Config: |
|
The limit specifies the number of failures that Squid tolerates when establishing a new TCP connection with an ICAP service. If the number of failures exceeds the limit, the ICAP service is not used for new ICAP requests until it is time to refresh its OPTIONS. A negative value disables the limit. Without the limit, an ICAP service will not be considered down due to connectivity failures between ICAP OPTIONS requests. Squid forgets ICAP service failures older than the specified value of memory-depth. The memory fading algorithm is approximate because Squid does not remember individual errors but groups them instead, splitting the option value into ten time slots of equal length. When memory-depth is 0 and by default this option has no effect on service failure expiration. Squid always forgets failures when updating service settings using an ICAP OPTIONS transaction, regardless of this option setting. For example, # suspend service usage after 10 failures in 5 seconds: icap_service_failure_limit 10 in 5 seconds |
|
Introduction
- About Squid
- Why Squid?
- Squid Developers
- How to Donate
- How to Help Out
- Getting Squid
- Squid Source Packages
- Squid Deployment Case-Studies
- Squid Software Foundation
Documentation
- Quick Setup
- Configuration:
- FAQ and Wiki
- Guide Books:
- Non-English
- More...
Support
- Security Advisories
- Bugzilla Database
- Mailing lists
- Contacting us
- Commercial services
- Project Sponsors
- Squid-based products
Miscellaneous
- Developer Resources
- Related Writings
- Related Software:
- Squid Artwork
Web Site Translations
Mirrors
- Website:
- gr il pl ... full list
- FTP Package Archive