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
46f4d0db
Commit
46f4d0db
authored
Feb 19, 2013
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
rework hiarchy
parent
47dc9d9e
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
7 additions
and
6 deletions
+7
-6
compression.rst
doc/sphinx/users-guide/compression.rst
+1
-1
purging.rst
doc/sphinx/users-guide/purging.rst
+4
-3
vary.rst
doc/sphinx/users-guide/vary.rst
+2
-2
No files found.
doc/sphinx/users-guide/compression.rst
View file @
46f4d0db
.. _users-guide-compression:
Compression
~~~~~~~~~~~
-----------
New in Varnish 3.0 was native support for compression, using gzip
encoding. *Before* 3.0, Varnish would never compress objects.
...
...
doc/sphinx/users-guide/purging.rst
View file @
46f4d0db
...
...
@@ -15,7 +15,7 @@ banning and forced cache misses. First, let me explain the HTTP purges.
HTTP Purges
-----------
~~~~~~~~~~~
A *purge* is what happens when you pick out an object from the cache
and discard it along with its variants. Usually a purge is invoked
...
...
@@ -75,7 +75,7 @@ And Varnish would then discard the front page. This will remove all
variants as defined by Vary.
Bans
----
~~~~
There is another way to invalidate content: Bans. You can think of
bans as a sort of a filter on objects already in the cache. You *ban*
...
...
@@ -164,7 +164,7 @@ be marked as Gone if it is a duplicate ban, but is still kept in the list
for optimization purposes.
Forcing a cache miss
--------------------
~~~~~~~~~~~~~~~~~~~~
The final way to invalidate an object is a method that allows you to
refresh an object by forcing a hash miss for a single request. If you set
...
...
@@ -173,3 +173,4 @@ cache, thus forcing a fetch from the backend. This can in turn add the
freshly fetched object to the cache, thus overriding the current one. The
old object will stay in the cache until ttl expires or it is evicted by
some other means.
doc/sphinx/users-guide/vary.rst
View file @
46f4d0db
.. _users-guide-vary:
Vary
~~~~
HTTP
Vary
---------
The Vary header is sent by the web server to indicate what makes a
HTTP object Vary. This makes a lot of sense with headers like
...
...
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