symfony
diff --git a/‎book/security.rst
Copy file name to clipboardExpand all lines: book/security.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎book/security.rst
Copy file name to clipboardExpand all lines: book/security.rst
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎components/class_loader/psr4_class_loader.rst
Copy file name to clipboardExpand all lines: components/class_loader/psr4_class_loader.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎components/class_loader/psr4_class_loader.rst
Copy file name to clipboardExpand all lines: components/class_loader/psr4_class_loader.rst
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎contributing/documentation/license.rst
Copy file name to clipboardExpand all lines: contributing/documentation/license.rst
+5-5Lines changed: 5 additions & 5 deletions b/‎contributing/documentation/license.rst
Copy file name to clipboardExpand all lines: contributing/documentation/license.rst
+5-5Lines changed: 5 additions & 5 deletions
diff --git a/‎cookbook/cache/varnish.rst
Copy file name to clipboardExpand all lines: cookbook/cache/varnish.rst
+8Lines changed: 8 additions & 0 deletions b/‎cookbook/cache/varnish.rst
Copy file name to clipboardExpand all lines: cookbook/cache/varnish.rst
+8Lines changed: 8 additions & 0 deletions
@@ -1105,7 +1105,7 @@ authorization from inside a controller::
     The ``createAccessDeniedException`` method was introduced in Symfony 2.5.
 
 The :method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::createAccessDeniedException`
-method creates a special :class:`Symfony\\Component\\Security\\Core\Exception\\AccessDeniedException`
+method creates a special :class:`Symfony\\Component\\Security\\Core\\Exception\\AccessDeniedException`
 object, which ultimately triggers a 403 HTTP response inside Symfony.
 
 Thanks to the SensioFrameworkExtraBundle, you can also secure your controller using annotations::
 
@@ -59,7 +59,7 @@ first need to configure the ``Psr4ClassLoader``:
 
 First of all, the class loader is loaded manually using a ``require``
 statement, since there is no autoload mechanism yet. With the
-:method:`Symfony\Component\ClassLoader\Psr4ClassLoader::addPrefix` call, you
+:method:`Symfony\\Component\\ClassLoader\\Psr4ClassLoader::addPrefix` call, you
 tell the class loader where to look for classes with the
 ``Symfony\Component\Yaml\`` namespace prefix. After registering the autoloader,
 the Yaml component is ready to be used.
 
@@ -32,13 +32,13 @@ Attribution-Share Alike 3.0 Unported `License`_.
 * *Other Rights* — In no way are any of the following rights affected by the
   license:
 
-    * Your fair dealing or fair use rights, or other applicable copyright
-      exceptions and limitations;
+  * Your fair dealing or fair use rights, or other applicable copyright exceptions
+    and limitations;
 
-    * The author's moral rights;
+  * The author's moral rights;
 
-    * Rights other persons may have either in the work itself or in how
-      the work is used, such as publicity or privacy rights.
+  * Rights other persons may have either in the work itself or in how the
+    work is used, such as publicity or privacy rights.
 
 * *Notice* — For any reuse or distribution, you must make clear to others
   the license terms of this work. The best way to do this is with a link
 
@@ -57,6 +57,14 @@ Symfony2 adds automatically:
             // For Varnish < 3.0
             // esi;
         }
+        /* By default Varnish ignores Cache-Control: nocache 
+        (https://www.varnish-cache.org/docs/3.0/tutorial/increasing_your_hitrate.html#cache-control),
+        so in order avoid caching it has to be done explicitly */
+        if (beresp.http.Pragma ~ "no-cache" ||
+             beresp.http.Cache-Control ~ "no-cache" ||
+             beresp.http.Cache-Control ~ "private") {
+            return (hit_for_pass);
+        }
     }
 
 .. caution::