Using Varnish

eZ Platform being built on top of Symfony, it uses standard HTTP= cache headers. By default the Symfony reverse proxy, written in PHP, is us= ed to handle cache, but it can be easily replaced with any other reverse pr= oxy like Varnish.

Use of Varnish is a requirement for use in Clustering setup, for ove= rview of clustering feature see Clustering.

=20

Prerequisites
Recommended VCL base = files
Configure eZ Publish= =20
- Update your Virtual Hos= t=20
  - On apache:
  - On nginx:
- Update YML configurati= on

=20

Prerequisites

A working Varnish 3 or Varnish 4 setup.

Recommended VCL base files<= /h2>
For Varnish to work properly with eZ, you'll need to use one of the prov= ided files as a basis:

Varnish 3 VC= L example

Varnish 4 VC= L example

Note: Http cache management is done with the help of FOSHttpCacheBundle. You may need to tweak your VCL f= urther on according to F= OSHttpCache documentation in order to use features supported by it.

Configure eZ Publish

Update your Virtual Host

On apache:

my_virtualhost.conf

=20

<VirthualHost *:80>
    # Configure your VirtualHost with rewrite rules and stuff
 
    # Force front controller NOT to use built-in reverse proxy.
    SetEnv USE_HTTP_CACHE 0
 
=09# Configure IP of your Varnish server to be trusted proxy
    # Replace fake IP address below by your Varnish IP address
    SetEnv TRUSTED_PROXIES "193.22.44.22"
</VirtualHost>

=20

On nginx:

mysite.com

=20

fastcgi_param USE_HTTP_CACHE 0;
# Configure IP of your Varnish server to be trusted proxy
# Replace fake IP address below by your Varnish IP address
fastcgi_param TRUSTED_PROXIES "193.22.44.22";

=20

Update YML configuration

ezplatform.yml

=20

ezpublish:
    http_cache:
        purge_type: http
 
    system:
        # Assuming that my_siteaccess_group your frontend AND backend sitea=
ccesses
        my_siteaccess_group:
            http_cache:
                # Fill in your Varnish server(s) address(es).
                purge_servers: [http://my.varnish.server:6081]

=20