Commit eacd8c32 authored by Tollef Fog Heen's avatar Tollef Fog Heen

Document that TTL is no longer taken into account for beresp.cacheable


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4669 d4fa192b-c00b-0410-8231-f00ffab90ce4
parent f65ff338
......@@ -586,13 +586,8 @@ The HTTP status message returned by the server.
.It Va obj.cacheable
True if the request resulted in a cacheable response.
.\" see cache_center.c and rfc2616.c for details
A response is considered cacheable if it is valid (see above), the
HTTP status code is 200, 203, 300, 301, 302, 404 or 410 and it has a
non-zero time-to-live when
.Cm Expires
and
.Cm Cache-Control
headers are taken into account.
A response is considered cacheable if it is valid (see above), and the
HTTP status code is 200, 203, 300, 301, 302, 404 or 410.
.It Va obj.ttl
The object's remaining time to live, in seconds.
.It Va obj.lastuse
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment