@@ -24,21 +24,14 @@ Create the cache invalidator by passing a proxy client as
2424
2525 $cacheInvalidator = new CacheInvalidator($client);
2626
27- Supported invalidation methods
28- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
29-
30- ============= ======= ======= =======
31- Client Purge Refresh Ban
32- ============= ======= ======= =======
33- Varnish ✓ ✓ ✓
34- NGINX ✓ ✓
35- Symfony Cache ✓ ✓
36- Noop ✓ ✓ ✓
37- ============= ======= ======= =======
38-
39- .. note ::
27+ Depending on the capabilities of the proxy client, some invalidation methods
28+ may not work. If you try to call an invalidation method that is not supported,
29+ an ``UnsupportedProxyOperationException `` is thrown. You can check for support
30+ by calling ``CacheInvalidator::support `` with the constant of the operation you
31+ need.
4032
41- See :ref: `proxy client setup <client setup >` for more on constructing a client.
33+ See :doc: `proxy clients <proxy-clients >` for the details on setting up the
34+ proxy client and an overview of the supported operations of each client.
4235
4336.. _cache invalidate :
4437
@@ -71,7 +64,7 @@ Invalidate a URL with added header(s)::
7164
7265.. include :: includes/custom-headers.rst
7366
74- Please note that purge will invalidate all variants, so you do not have to
67+ Please note that purge will invalidate all variants, so you do not need to
7568send any headers that you vary on, such as ``Accept ``.
7669
7770.. _cache refresh :
@@ -167,9 +160,9 @@ You can also invalidate the cache based on any headers.
167160Proxy client implementations should fill up the headers to at least have the
168161default headers always present to simplify the cache configuration rules.
169162
170- To invalidate on a custom header ``X- My-Header ``, you would do::
163+ To invalidate on a custom header ``My-Header ``, you would do::
171164
172- $cacheInvalidator->invalidate(['X- My-Header' => 'my-value'])->flush();
165+ $cacheInvalidator->invalidate(['My-Header' => 'my-value'])->flush();
173166
174167.. _flush :
175168
0 commit comments