@@ -400,6 +400,7 @@ header when none is set by the developer by following these rules:
400
400
``private `` directive automatically (except when ``s-maxage `` is set).
401
401
402
402
.. _http-expiration-validation :
403
+ .. _http-expiration-and-validation :
403
404
404
405
HTTP Expiration, Validation and Invalidation
405
406
--------------------------------------------
@@ -775,7 +776,7 @@ at some interval (the expiration) to verify that the content is still valid.
775
776
annotations. See the `FrameworkExtraBundle documentation `_.
776
777
777
778
.. index ::
778
- pair: Cache; Configuration
779
+ pair: Cache; Configuration
779
780
780
781
More Response Methods
781
782
~~~~~~~~~~~~~~~~~~~~~
@@ -803,7 +804,7 @@ Additionally, most cache-related HTTP headers can be set via the single
803
804
));
804
805
805
806
.. index ::
806
- single: Cache; Invalidation
807
+ single: Cache; Invalidation
807
808
808
809
.. _http-cache-invalidation :
809
810
@@ -821,7 +822,7 @@ cache lifetimes, but to actively notify the gateway cache when content
821
822
changes. Reverse proxies usually provide a channel to receive such
822
823
notifications, typically through special HTTP requests.
823
824
824
- .. warning ::
825
+ .. caution ::
825
826
826
827
While cache invalidation is powerful, avoid it when possible. If you fail
827
828
to invalidate something, outdated caches will be served for a potentially
@@ -846,7 +847,8 @@ that data from its cache.
846
847
a couple of common caching proxies.
847
848
848
849
If 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
850
852
of ``GET `` and make the cache proxy detect this and remove the data from the
851
853
cache instead of going to Symfony to get a response.
852
854
@@ -899,13 +901,13 @@ In many applications, the same content bit is used on various pages with
899
901
different URLs. More flexible concepts exist for those cases:
900
902
901
903
* **Banning ** invalidates responses matching regular expressions on the
902
- URL or other criteria.
904
+ URL or other criteria;
903
905
* **Cache tagging ** lets you add a tag for each content used in a response
904
906
so that you can invalidate all URLs containing a certain content.
905
907
906
908
.. index ::
907
- single: Cache; ESI
908
- single: ESI
909
+ single: Cache; ESI
910
+ single: ESI
909
911
910
912
.. _edge-side-includes :
911
913
0 commit comments