r4828 - trunk/varnish-cache/doc/sphinx/tutorial

perbu at varnish-cache.org perbu at varnish-cache.org
Wed May 19 14:35:36 CEST 2010

Author: perbu
Date: 2010-05-19 14:35:36 +0200 (Wed, 19 May 2010)
New Revision: 4828

authorization and normalizing namespace

Modified: trunk/varnish-cache/doc/sphinx/tutorial/increasing_your_hitrate.rst
--- trunk/varnish-cache/doc/sphinx/tutorial/increasing_your_hitrate.rst	2010-05-19 10:42:37 UTC (rev 4827)
+++ trunk/varnish-cache/doc/sphinx/tutorial/increasing_your_hitrate.rst	2010-05-19 12:35:36 UTC (rev 4828)
@@ -52,9 +52,10 @@
 to vg.no and their somewhat odd sense of humour. Others, like the
 X-VG-Webcache are for debugging purposes. 
-So, to check whether a site sets cookies for a specific URL just do
-``GET -Used http://example.com/ |grep ^Set-Cookie``
+So, to check whether a site sets cookies for a specific URL just do::
+  GET -Used http://example.com/ |grep ^Set-Cookie
 Firefox plugins
@@ -214,13 +215,27 @@
+If Varnish sees a Authorization header it will pass the request. If
+this is not what you want you can unset the header.
 Normalizing your namespace
+Some sites are accessed via lots of
+hostnames. http://www.varnish-software.com ,
+http://varnish-software.com and http://varnishsoftware.com/ all point
+at the same site. Since Varnish doesn't know they are different
+Varnish will cache different versions of every page for every
+hostname. You can mitigate this in your web server config by setting
+up redirects or by useing the following VCL:::
+  if (req.http.host ~ "^(www.)?varnish-?software.com") {
+    set req.http.host = "varnish-software.com";
+  }
 .. _tutorial-increasing_your_hitrate-purging:

More information about the varnish-commit mailing list