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
850f1165
Commit
850f1165
authored
Feb 27, 2013
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
language cleanup
parent
22b7b856
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
5 deletions
+3
-5
vcl-intro.rst
doc/sphinx/users-guide/vcl-intro.rst
+3
-5
No files found.
doc/sphinx/users-guide/vcl-intro.rst
View file @
850f1165
...
...
@@ -13,18 +13,16 @@ are executed at different times. One is executed when we get the
request, another when files are fetched from the backend server.
Varnish will execute these subroutines of code at different stages of
its work. Because it is code it is execute line by line precedence
isn't a problem. At some point you call an action in this subroutine
and then the execution of the subroutine stops.
its work. At some point you call an action in this subroutine and then
the execution of that subroutine stops.
If you don't call an action in your subroutine and it reaches the end
Varnish will execute
som
e built in VCL code. You will see this VCL
Varnish will execute
th
e built in VCL code. You will see this VCL
code commented out in default.vcl.
99% of all the changes you'll need to do will be done in two of these
subroutines. *vcl_recv* and *vcl_fetch*.
.. _users-guide-vcl_fetch_actions:
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