Skip to content

[Cookbook][Cache] add syntax highlighting for Varnish code blocks #4481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 18, 2014
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions cookbook/cache/varnish.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ First, configure Varnish so that it advertises its ESI support by adding a
``Surrogate-Capability`` header to requests forwarded to the backend
application:

.. code-block:: text
.. code-block:: varnish4

sub vcl_recv {
// Add a Surrogate-Capability header to announce ESI support.
Expand Down Expand Up @@ -137,7 +137,7 @@ proxy before it has expired, it adds complexity to your caching setup.
Varnish can be configured to accept a special HTTP ``PURGE`` method
that will invalidate the cache for a given resource:

.. code-block:: text
.. code-block:: varnish4

/*
Connect to the backend server
Expand Down Expand Up @@ -186,7 +186,7 @@ that will invalidate the cache for a given resource:
You must protect the ``PURGE`` HTTP method somehow to avoid random people
purging your cached data. You can do this by setting up an access list:

.. code-block:: text
.. code-block:: varnish4

/*
Connect to the backend server
Expand Down Expand Up @@ -252,7 +252,7 @@ is 80 and not 8080.
If this header weren't set properly, Symfony may append ``8080`` when generating
absolute URLs:

.. code-block:: text
.. code-block:: varnish4

sub vcl_recv {
if (req.http.X-Forwarded-Proto == "https" ) {
Expand Down