Squid configuration directive adaptation_masterx_shared_names
Available in: v7 v6 v5 v4 3.5 3.4 3.3 3.2 3.1
For older versions than v4 see the linked pages above
Configuration Details:
Option Name: | adaptation_masterx_shared_names |
---|---|
Replaces: | |
Requires: | --enable-ecap or --enable-icap-client |
Default Value: | none |
Suggested Config: |
# share authentication information among ICAP services |
For each master transaction (i.e., the HTTP request and response sequence, including all related ICAP and eCAP exchanges), Squid maintains a table of metadata. The table entries are (name, value) pairs shared among eCAP and ICAP exchanges. The table is destroyed with the master transaction. This option specifies the table entry names that Squid must accept from and forward to the adaptation transactions. An ICAP REQMOD or RESPMOD transaction may set an entry in the shared table by returning an ICAP header field with a name specified in adaptation_masterx_shared_names. An eCAP REQMOD or RESPMOD transaction may set an entry in the shared table by implementing the libecap::visitEachOption() API to provide an option with a name specified in adaptation_masterx_shared_names. Squid will store and forward the set entry to subsequent adaptation transactions within the same master transaction scope. Only one shared entry name is supported at this time. Example: adaptation_masterx_shared_names X-Subscriber-ID |
|
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