[3.0] 9f2dcde obj and beresp.cacheable are gone
Tollef Fog Heen
tfheen at varnish-cache.org
Mon Jul 11 10:16:57 CEST 2011
commit 9f2dcdeade83e3755573923310e6e56265c22d55
Author: Per Buer <perbu at varnish-software.com>
Date: Wed Jun 29 23:14:22 2011 +0200
obj and beresp.cacheable are gone
diff --git a/doc/sphinx/reference/vcl.rst b/doc/sphinx/reference/vcl.rst
index 8861404..b9aaddc 100644
--- a/doc/sphinx/reference/vcl.rst
+++ b/doc/sphinx/reference/vcl.rst
@@ -681,15 +681,6 @@ beresp.status
beresp.response
The HTTP status message returned by the server.
-beresp.cacheable
- True if the request resulted in a cacheable response. A response is
- considered cacheable if HTTP status code is 200, 203, 300, 301, 302,
- 404 or 410 and pass wasn't called in vcl_recv. If however, both the
- TTL and the grace time for the response are 0 beresp.cacheable will
- be 0.
-
- beresp.cacheable is writable.
-
beresp.ttl
The object's remaining time to live, in seconds. beresp.ttl is writable.
@@ -706,10 +697,6 @@ obj.status
obj.response
The HTTP status message returned by the server.
-obj.cacheable
- True if the object had beresp.cacheable. Unless you've forced delivery
- in your VCL obj.cacheable will always be true.
-
obj.ttl
The object's remaining time to live, in seconds. obj.ttl is writable.
More information about the varnish-commit
mailing list