From 9260bc143463ac31a02f46ce3f65b0651d58ceb1 Mon Sep 17 00:00:00 2001 From: Zairig Imad Date: Wed, 24 Jun 2020 20:53:19 +0200 Subject: [PATCH] Update cache_invalidation.rst --- http_cache/cache_invalidation.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/http_cache/cache_invalidation.rst b/http_cache/cache_invalidation.rst index 764ccd09610..02d5f33bb06 100644 --- a/http_cache/cache_invalidation.rst +++ b/http_cache/cache_invalidation.rst @@ -88,7 +88,7 @@ Here is how you can configure the Symfony reverse proxy to support the purging your cached data. **Purge** instructs the cache to drop a resource in *all its variants* -(according to the ``Vary`` header, see above). An alternative to purging is +(according to the ``Vary`` header, see :doc:`/http_cache/cache_vary`). An alternative to purging is **refreshing** a content. Refreshing means that the caching proxy is instructed to discard its local cache and fetch the content again. This way, the new content is already available in the cache. The drawback of refreshing