minor #99 Rename cache/ to http_cache/ (WouterJ)

This PR was merged into the 2.7 branch.

Discussion
----------

Rename cache/ to http_cache/

To match the article name and make a free place for Cache component related guides

Commits
-------

837adff Rename cache/ to http_cache/

Author: javiereguiluz

form/csrf_protection.rst

@@ -67,6 +67,6 @@ section.
     CSRF tokens are meant to be different for every user. This is why you
     need to be cautious if you try to cache pages with forms including this
     kind of protection. For more information, see
-    :doc:`/cache/form_csrf_caching`.
+    :doc:`/http_cache/form_csrf_caching`.
 
 .. _`Cross-site request forgery`: http://en.wikipedia.org/wiki/Cross-site_request_forgery

forms.rst

@@ -726,7 +726,7 @@ Learn more
 
 * :doc:`/controller/upload_file`
 * :doc:`/reference/forms/types`
-* :doc:`/cache/form_csrf_caching`
+* :doc:`/http_cache/form_csrf_caching`
 
 .. _`Symfony Form component`: https://github.com/symfony/form
 .. _`DateTime`: http://php.net/manual/en/class.datetime.php

http_cache.rst

@@ -15,7 +15,7 @@ Caching on the Shoulders of Giants
 With HTTP Caching, you cache the full output of a page (i.e. the response) and bypass
 your application *entirely* on subsequent requests. Of course, caching entire responses
 isn't always possible for highly dynamic sites, or is it? With
-:doc:`Edge Side Includes (ESI) </cache/esi>`, you can use the power of HTTP caching
+:doc:`Edge Side Includes (ESI) </http_cache/esi>`, you can use the power of HTTP caching
 on only *fragments* of your site.
 
 The Symfony cache system is different because it relies on the simplicity
@@ -76,7 +76,7 @@ but is a great way to start.
 
 .. tip::
 
-    For details on setting up Varnish, see :doc:`/cache/varnish`.
+    For details on setting up Varnish, see :doc:`/http_cache/varnish`.
 
 Enabling the proxy is easy: each application comes with a caching kernel (``AppCache``)
 that wraps the default one (``AppKernel``). The caching Kernel *is* the reverse
@@ -153,7 +153,7 @@ information about cache hits and misses.
 
     Fortunately, since all reverse proxies are effectively the same, you should
     be able to switch to something more robust - like Varnish - without any problems.
-    See :doc:`How to use Varnish </cache/varnish>`
+    See :doc:`How to use Varnish </http_cache/varnish>`
 
 .. index::
    single: Cache; HTTP
@@ -242,7 +242,7 @@ for debugging information about cache hits and misses.
 
 .. tip::
 
-    The URI of the request is used as the cache key (unless you :doc:`vary </cache/cache_vary>`).
+    The URI of the request is used as the cache key (unless you :doc:`vary </http_cache/cache_vary>`).
 
 This is *super* performant and simple to use. But, cache *invalidation* is not supported.
 If your content change, you'll need to wait until your cache expires for the page
@@ -257,7 +257,7 @@ If you need to set cache headers for many different controller actions, check ou
 `FOSHttpCacheBundle`_. It provides a way to define cache headers based on the URL
 pattern and other request properties.
 
-Finally, for more information about expiration caching, see :doc:`/cache/expiration`.
+Finally, for more information about expiration caching, see :doc:`/http_cache/expiration`.
 
 .. _http-cache-validation-intro:
 
@@ -276,7 +276,7 @@ If you need to see updated content *immediately*, you either need to
 :ref:`invalidate <http-cache-invalidation>` your cache *or* use the validation
 caching model.
 
-For details, see :doc:`/cache/validation`.
+For details, see :doc:`/http_cache/validation`.
 
 .. index::
    single: Cache; Safe methods
@@ -331,13 +331,13 @@ Cache invalidation is *not* part of the HTTP specification. Still, it can be rea
 useful to delete various HTTP cache entries as soon as some content on your site
 is updated.
 
-For details, see :doc:`/cache/cache_invalidation`.
+For details, see :doc:`/http_cache/cache_invalidation`.
 
 Using Edge Side Includes
 ------------------------
 
 When pages contain dynamic parts, you may not be able to cache entire pages,
-but only parts of it. Read :doc:`/cache/esi` to find out how to configure
+but only parts of it. Read :doc:`/http_cache/esi` to find out how to configure
 different cache strategies for specific parts of your page.
 
 Summary
@@ -357,7 +357,7 @@ Learn more
     :maxdepth: 1
     :glob:
 
-    cache/*
+    http_cache/*
 
 .. _`Things Caches Do`: http://2ndscale.com/writings/things-caches-do
 .. _`Cache Tutorial`: http://www.mnot.net/cache_docs/

cache/cache_invalidation.rst renamed to http_cache/cache_invalidation.rst

@@ -29,7 +29,7 @@ How to Cache Most of the Page and still be able to Use CSRF Protection
 ----------------------------------------------------------------------
 
 To cache a page that contains a CSRF token, you can use more advanced caching
-techniques like :doc:`ESI fragments </cache/esi>`, where you cache the full
+techniques like :doc:`ESI fragments </http_cache/esi>`, where you cache the full
 page and embedding the form inside an ESI tag with no cache at all.
 
 Another option would be to load the form via an uncached AJAX request, but
@@ -39,4 +39,4 @@ Or you can even load just the CSRF token with an AJAX request and replace the
 form field value with it.
 
 .. _`Cross-site request forgery`: http://en.wikipedia.org/wiki/Cross-site_request_forgery
-.. _`Security CSRF Component`: https://github.com/symfony/security-csrf
+.. _`Security CSRF Component`: https://github.com/symfony/security-csrf

cache/cache_vary.rst renamed to http_cache/cache_vary.rst

@@ -228,5 +228,6 @@ the response status code to ``304``, removes the content, and removes some
 headers that must not be present for ``304`` responses (see
 :method:`Symfony\\Component\\HttpFoundation\\Response::setNotModified`).
 
+.. _`expiration model`: https://tools.ietf.org/html/rfc2616#section-13.2
 .. _`validation model`: http://tools.ietf.org/html/rfc2616#section-13.3
 .. _`FrameworkExtraBundle documentation`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/cache.html

cache/esi.rst renamed to http_cache/esi.rst

@@ -7,7 +7,7 @@ How to Use Varnish to Speed up my Website
 Because Symfony's cache uses the standard HTTP cache headers, the
 :ref:`symfony-gateway-cache` can easily be replaced with any other reverse
 proxy. `Varnish`_ is a powerful, open-source, HTTP accelerator capable of serving
-cached content fast and including support for :doc:`Edge Side Includes </cache/esi>`.
+cached content fast and including support for :doc:`Edge Side Includes </http_cache/esi>`.
 
 .. index::
     single: Varnish; configuration
@@ -80,7 +80,7 @@ at least for some parts of the site, e.g. when using forms with
 :doc:`CSRF Protection </form/csrf_protection>`. In this situation, make sure to
 :doc:`only start a session when actually needed </session/avoid_session_start>`
 and clear the session when it is no longer needed. Alternatively, you can look
-into :doc:`/cache/form_csrf_caching`.
+into :doc:`/http_cache/form_csrf_caching`.
 
 Cookies created in JavaScript and used only in the frontend, e.g. when using
 Google Analytics, are nonetheless sent to the server. These cookies are not
@@ -168,7 +168,7 @@ using Varnish 3:
 Enable Edge Side Includes (ESI)
 -------------------------------
 
-As explained in the :doc:`Edge Side Includes chapter </cache/esi>`, Symfony
+As explained in the :doc:`Edge Side Includes chapter </http_cache/esi>`, Symfony
 detects whether it talks to a reverse proxy that understands ESI or not. When
 you use the Symfony reverse proxy, you don't need to do anything. But to make
 Varnish instead of Symfony resolve the ESI tags, you need some configuration