Squid configuration directive negative_ttl
Available in: 3.3 3.2 3.1 2.7 3.HEAD 2.HEAD 3.0 2.6
History:
- Changes in 3.1 negative_ttl
-
New default of 0 seconds. To prevent negative-caching of failure messages unless explicitly permitted by the message generating web server.
Changing this is an RFC 2616 violation and now requires --enable-http-violations
Configuration Details:
Option Name: | negative_ttl |
---|---|
Replaces: | |
Requires: | --enable-http-violations |
Default Value: | negative_ttl 0 seconds |
Suggested Config: |
|
Set the Default Time-to-Live (TTL) for failed requests. Certain types of failures (such as "connection refused" and "404 Not Found") are able to be negatively-cached for a short time. Modern web servers should provide Expires: header, however if they do not this can provide a minimum TTL. The default is not to cache errors with unknown expiry details. Note that this is different from negative caching of DNS lookups. WARNING: Doing this VIOLATES the HTTP standard. Enabling this feature could make you liable for problems which it causes. |
|
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