Commit 9f2dcdea authored by Per Buer's avatar Per Buer Committed by Tollef Fog Heen

obj and beresp.cacheable are gone

parent 48874f83
......@@ -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.
......
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