Skip to content

Commit 5f8f7b8

Browse files
committed
minor #13897 Update cache_invalidation.rst (zairigimad)
This PR was submitted for the 5.0 branch but it was squashed and merged into the 3.4 branch instead. Discussion ---------- Update cache_invalidation.rst <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- 9260bc1 Update cache_invalidation.rst
2 parents 73161b8 + 9260bc1 commit 5f8f7b8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

http_cache/cache_invalidation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ Here is how you can configure the Symfony reverse proxy to support the
8888
purging your cached data.
8989

9090
**Purge** instructs the cache to drop a resource in *all its variants*
91-
(according to the ``Vary`` header, see above). An alternative to purging is
91+
(according to the ``Vary`` header, see :doc:`/http_cache/cache_vary`). An alternative to purging is
9292
**refreshing** a content. Refreshing means that the caching proxy is
9393
instructed to discard its local cache and fetch the content again. This way,
9494
the new content is already available in the cache. The drawback of refreshing

0 commit comments

Comments
 (0)