@@ -400,6 +400,7 @@ header when none is set by the developer by following these rules:
400400 ``private `` directive automatically (except when ``s-maxage `` is set).
401401
402402.. _http-expiration-validation :
403+ .. _http-expiration-and-validation :
403404
404405HTTP Expiration, Validation and Invalidation
405406--------------------------------------------
@@ -775,7 +776,7 @@ at some interval (the expiration) to verify that the content is still valid.
775776 annotations. See the `FrameworkExtraBundle documentation `_.
776777
777778.. index ::
778- pair: Cache; Configuration
779+ pair: Cache; Configuration
779780
780781More Response Methods
781782~~~~~~~~~~~~~~~~~~~~~
@@ -803,7 +804,7 @@ Additionally, most cache-related HTTP headers can be set via the single
803804 ));
804805
805806.. index ::
806- single: Cache; Invalidation
807+ single: Cache; Invalidation
807808
808809.. _http-cache-invalidation :
809810
@@ -821,7 +822,7 @@ cache lifetimes, but to actively notify the gateway cache when content
821822changes. Reverse proxies usually provide a channel to receive such
822823notifications, typically through special HTTP requests.
823824
824- .. warning ::
825+ .. caution ::
825826
826827 While cache invalidation is powerful, avoid it when possible. If you fail
827828 to invalidate something, outdated caches will be served for a potentially
@@ -846,7 +847,8 @@ that data from its cache.
846847 a couple of common caching proxies.
847848
848849If one content corresponds to one URL, the ``PURGE `` model works well.
849- You send a request to the cache proxy with the HTTP method ``PURGE `` instead
850+ You send a request to the cache proxy with the HTTP method ``PURGE `` (using
851+ the word "PURGE" is a convention, technically this can be any string) instead
850852of ``GET `` and make the cache proxy detect this and remove the data from the
851853cache instead of going to Symfony to get a response.
852854
@@ -899,13 +901,13 @@ In many applications, the same content bit is used on various pages with
899901different URLs. More flexible concepts exist for those cases:
900902
901903* **Banning ** invalidates responses matching regular expressions on the
902- URL or other criteria.
904+ URL or other criteria;
903905* **Cache tagging ** lets you add a tag for each content used in a response
904906 so that you can invalidate all URLs containing a certain content.
905907
906908.. index ::
907- single: Cache; ESI
908- single: ESI
909+ single: Cache; ESI
910+ single: ESI
909911
910912.. _edge-side-includes :
911913
0 commit comments