File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -38,7 +38,7 @@ First, configure Varnish so that it advertises its ESI support by adding a
38
38
``Surrogate-Capability `` header to requests forwarded to the backend
39
39
application:
40
40
41
- .. code-block :: text
41
+ .. code-block :: varnish4
42
42
43
43
sub vcl_recv {
44
44
// Add a Surrogate-Capability header to announce ESI support.
@@ -137,7 +137,7 @@ proxy before it has expired, it adds complexity to your caching setup.
137
137
Varnish can be configured to accept a special HTTP ``PURGE `` method
138
138
that will invalidate the cache for a given resource:
139
139
140
- .. code-block :: text
140
+ .. code-block :: varnish4
141
141
142
142
/*
143
143
Connect to the backend server
@@ -186,7 +186,7 @@ that will invalidate the cache for a given resource:
186
186
You must protect the ``PURGE `` HTTP method somehow to avoid random people
187
187
purging your cached data. You can do this by setting up an access list:
188
188
189
- .. code-block :: text
189
+ .. code-block :: varnish4
190
190
191
191
/*
192
192
Connect to the backend server
@@ -252,7 +252,7 @@ is 80 and not 8080.
252
252
If this header weren't set properly, Symfony may append ``8080 `` when generating
253
253
absolute URLs:
254
254
255
- .. code-block :: text
255
+ .. code-block :: varnish4
256
256
257
257
sub vcl_recv {
258
258
if (req.http.X-Forwarded-Proto == "https" ) {
You can’t perform that action at this time.
0 commit comments