@@ -4,18 +4,21 @@ Caching Proxy Clients
4
4
You can use the caching proxy clients either wrapped by the cache invalidator
5
5
(recommended), or directly for low-level access to invalidation functionality.
6
6
7
+ * [ Setup] ( #setup )
8
+ * [ CacheProxyInterface] ( #cacheproxyinterface )
9
+ * [ Purge] ( #purge )
10
+ * [ Refresh] ( #refresh )
11
+ * [ Ban] ( #ban )
12
+
13
+ Setup
14
+ -----
15
+
7
16
You should set up at least one caching proxy client:
8
17
9
18
* [ Varnish client] ( varnish-client.md )
10
- * [ Nginx client] ( nginx-client.md )
19
+ * Nginx client
11
20
12
- Continue reading here for general information about the interfaces that are
13
- implemented by the clients.
14
-
15
- * [ CacheProxyInterface] ( #cacheproxyinterface )
16
- * [ PurgeInterface] ( #purgeinterface )
17
- * [ RefreshInterface] ( #refreshinterface )
18
- * [ BanInterface] ( #baninterface )
21
+ Then continue here to find out how to use the proxy clients.
19
22
20
23
CacheProxyInterface
21
24
-------------------
@@ -32,8 +35,8 @@ requests to the caching proxy. This is on purpose: this way, we can send
32
35
all requests together, reducing the performance impact of sending invalidation
33
36
requests.
34
37
35
- PurgeInterface
36
- --------------
38
+ Purge
39
+ -----
37
40
38
41
If the caching proxy understands [ purge requests] ( invalidation-introduction.md#purge ) ,
39
42
its client should implement ` PurgeInterface ` . Use the ` purge($url) ` method to
@@ -48,8 +51,8 @@ $client
48
51
;
49
52
```
50
53
51
- RefreshInterface
52
- ----------------
54
+ Refresh
55
+ -------
53
56
54
57
If the caching proxy understands [ refresh requests] ( invalidation-introduction.md#refresh ) ,
55
58
its client should implement ` RefreshInterface ` . Use the
@@ -74,8 +77,8 @@ $client
74
77
;
75
78
```
76
79
77
- BanInterface
78
- ------------
80
+ Ban
81
+ ---
79
82
80
83
If the caching proxy understands [ ban requests] ( invalidation-introduction.md#ban ) ,
81
84
its client should implement ` BanInterface ` .
0 commit comments