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
05d0d530
Commit
05d0d530
authored
Feb 20, 2014
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
rewrite for readability
parent
79a0da1f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
introduction.rst
doc/sphinx/tutorial/introduction.rst
+9
-9
No files found.
doc/sphinx/tutorial/introduction.rst
View file @
05d0d530
...
...
@@ -8,23 +8,23 @@ clients and tries to answer them from its cache. If it cannot answer
the request from its cache it will forward the request to the backend,
fetch the response, store it and deliver it to the client.
When Varnish has a cached response ready it is typically delivered in
a matter of microseconds, several orders of magnitude faster than your
typical application server, so you want to make sure to have it answer
as many of the requests as possible.
Varnish decides whether it can store the content or not based on the
response it's gets back from the backend. The backend can instruct
Varnish to cache the content with the HTTP response header
Cache-Control.
Varnish will be very careful when it encounters cookies, either coming
from the client or from the origin server. When Varnish sees a
Set-Cookie header on a response it decides that the object is not
cacheable. When there is a Cookie header in the request it will also
refuse to serve a cached object and rather ask the backend for version
of the object that is tailored to the request.
Cache-Control. There are a few other conditions where Varnish will not
cache, the most common one being cookies. Since cookies is a good
indication that a web object is personlised, Varnish will with it's
default configuration, not cache it.
This behaviour and most other behaviour can be changed using policies
written in the Varnish Configuration Language. See the Users Guide
for more information on how to do that.
Performance
~~~~~~~~~~~
...
...
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