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
03893a97
Commit
03893a97
authored
Feb 21, 2014
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
4.0 updates
parent
f03a993b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
1 deletion
+10
-1
vcl-actions.rst
doc/sphinx/users-guide/vcl-actions.rst
+10
-1
No files found.
doc/sphinx/users-guide/vcl-actions.rst
View file @
03893a97
...
...
@@ -21,7 +21,7 @@ The most common actions to return are these:
*lookup*
When you return lookup from vcl_recv you tell Varnish to deliver content
from cache even if the request othervise indicates that the request
should be passed.
You can't return lookup from vcl_fetch.
should be passed.
*pipe*
Pipe can be returned from vcl_recv as well. Pipe short circuits the
...
...
@@ -34,3 +34,12 @@ The most common actions to return are these:
*deliver*
Deliver the cached object to the client. Usually returned from vcl_fetch.
*restart*
Restart processing of the request. You can restart the processing of
the whole transaction. Changes to the req object are retained.
*retry*
Retry the request against the backend. This can be called from
vcl_backend_response or vcl_backend_error if you don't like the response
that the backend delivered.
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