Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
91023bb8
Commit
91023bb8
authored
Jun 29, 2011
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
obj and beresp.cacheable are gone
parent
9cc19dd7
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
13 deletions
+0
-13
vcl.rst
doc/sphinx/reference/vcl.rst
+0
-13
No files found.
doc/sphinx/reference/vcl.rst
View file @
91023bb8
...
...
@@ -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.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment