Squid configuration directive icap_access
Available in: 3.3 3.2 3.1 3.HEAD 3.0
History:
- Changes in 3.1 icap_access
-
Replaced by adaptation_access.
- Changes in 3.0 icap_access
-
Default: none Redirects a request through an ICAP service class, depending on given acls icap_access classname allow|deny [!]aclname... The icap_access statements are processed in the order they appear in this configuration file. If an access list matches, the processing stops. For an "allow" rule, the specified class is used for the request. A "deny" rule simply stops processing without using the class. You can also use the special classname "None". For backward compatibility, it is also possible to use services directly here. Example: icap_access class_1 allow all
Configuration Details:
Option Name: | icap_access |
---|---|
Replaces: | |
Requires: | --enable-icap-client |
Default Value: | none |
Suggested Config: |
|
This option is deprecated. Please use adaptation_access, which has the same ICAP functionality, but comes with better documentation, and eCAP support. |
|
Search
Introduction
- About Squid
- Why Squid?
- Squid Developers
- How to Help Out or Donate
- Getting Squid
- Squid Source Packages
- Squid Deployment Case-Studies
- Squid Software Foundation
Documentation
- 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