Squid configuration directive cache_miss_revalidate
Available in: v7 v6 v5 v4 3.5 3.4 3.3
For older versions than v4 see the linked pages above
Configuration Details:
Option Name: | cache_miss_revalidate |
---|---|
Replaces: | |
Requires: | |
Default Value: | cache_miss_revalidate on |
Suggested Config: |
|
RFC 7232 defines a conditional request mechanism to prevent response objects being unnecessarily transferred over the network. If that mechanism is used by the client and a cache MISS occurs it can prevent new cache entries being created. This option determines whether Squid on cache MISS will pass the client revalidation request to the server or tries to fetch new content for caching. It can be useful while the cache is mostly empty to more quickly have the cache populated by generating non-conditional GETs. When set to 'on' (default), Squid will pass all client If-* headers to the server. This permits server responses without a cacheable payload to be delivered and on MISS no new cache entry is created. When set to 'off' and if the request is cacheable, Squid will remove the clients If-Modified-Since and If-None-Match headers from the request sent to the server. This requests a 200 status response from the server to create a new cache entry with. |
|
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:
- ... full list
- FTP Package Archive