[master] 46f4d0d rework hiarchy

Per Buer perbu at varnish-cache.org
Tue Feb 19 17:50:09 CET 2013

commit 46f4d0dbb195be32a40734abdf46a9b635e39c80
Author: Per Buer <perbu at varnish-software.com>
Date:   Tue Feb 19 17:51:07 2013 +0100

    rework hiarchy

diff --git a/doc/sphinx/users-guide/compression.rst b/doc/sphinx/users-guide/compression.rst
index 1e93384..0b78893 100644
--- a/doc/sphinx/users-guide/compression.rst
+++ b/doc/sphinx/users-guide/compression.rst
@@ -1,7 +1,7 @@
 .. _users-guide-compression:
 New in Varnish 3.0 was native support for compression, using gzip
 encoding. *Before* 3.0, Varnish would never compress objects. 
diff --git a/doc/sphinx/users-guide/purging.rst b/doc/sphinx/users-guide/purging.rst
index 2402632..668cacf 100644
--- a/doc/sphinx/users-guide/purging.rst
+++ b/doc/sphinx/users-guide/purging.rst
@@ -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.
 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.
diff --git a/doc/sphinx/users-guide/vary.rst b/doc/sphinx/users-guide/vary.rst
index 8b6fa2b..4f4f475 100644
--- a/doc/sphinx/users-guide/vary.rst
+++ b/doc/sphinx/users-guide/vary.rst
@@ -1,7 +1,7 @@
 .. _users-guide-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

More information about the varnish-commit mailing list