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
09b77e3a
Commit
09b77e3a
authored
Feb 29, 2012
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
backend cookies
parent
21e653c3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
0 deletions
+12
-0
cookies.rst
doc/sphinx/tutorial/cookies.rst
+12
-0
No files found.
doc/sphinx/tutorial/cookies.rst
View file @
09b77e3a
...
...
@@ -13,6 +13,9 @@ This can be overly conservative. A lot of sites use Google Analytics
cookie is used by the client side javascript and is therefore of no
interest to the server.
Cookies from the client
~~~~~~~~~~~~~~~~~~~~~~~
For a lot of web application it makes sense to completely disregard the
cookies unless you are accessing a special part of the web site. This
VCL snippet in vcl_recv will disregard cookies unless you are
...
...
@@ -63,3 +66,12 @@ cookies named COOKIE1 and COOKIE2 and you can marvel at it::
The example is taken from the Varnish Wiki, where you can find other
scary examples of what can be done in VCL.
Cookies coming from the backend
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If your backend server sets a cookie using the Set-Cookie header
Varnish will not cache the page. A hit-for-pass object (see
:ref:`tutorial_vcl_fetch_actions`) is created. So, if the backend
server acts silly and sets unwanted cookies just unset the Set-Cookie
header and all should be fine.
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