a Symfony Product

The PHP micro-framework
based on the Symfony Components

Silex is in maintenance mode. Ends of life is set to June 2018.
Use Symfony 4 instead. Read more on Symfony's blog.
You are reading the documentation for Silex 2.0. Switch to the documentation for Silex 1.3.

Questions & Feedback


Creative Commons License Silex documentation is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.

HTTP Cache

The HttpCacheServiceProvider provides support for the Symfony Reverse Proxy.


  • http_cache.cache_dir: The cache directory to store the HTTP cache data.
  • http_cache.options (optional): An array of options for the HttpCache constructor.


  • http_cache: An instance of HttpCache.
  • http_cache.esi: An instance of Esi, that implements the ESI capabilities to Request and Response instances.
  • http_cache.store: An instance of Store, that implements all the logic for storing cache metadata (Request and Response headers).


$app->register(new Silex\Provider\HttpCacheServiceProvider(), array(
    'http_cache.cache_dir' => __DIR__.'/cache/',


Silex already supports any reverse proxy like Varnish out of the box by setting Response HTTP cache headers:

use Symfony\Component\HttpFoundation\Response;

$app->get('/', function() {
    return new Response('Foo', 200, array(
        'Cache-Control' => 's-maxage=5',


If you want Silex to trust the X-Forwarded-For* headers from your reverse proxy at address $ip, you will need to whitelist it as documented in Trusting Proxies.

If you would be running Varnish in front of your application on the same machine:

use Symfony\Component\HttpFoundation\Request;

Request::setTrustedProxies(array('', '::1'));

This provider allows you to use the Symfony reverse proxy natively with Silex applications by using the http_cache service. The Symfony reverse proxy acts much like any other proxy would, so you will want to whitelist it:

use Symfony\Component\HttpFoundation\Request;


The provider also provides ESI support:

$app->get('/', function() {
    $response = new Response(<<<EOF
        <esi:include src="/included" />

    , 200, array(
        'Surrogate-Control' => 'content="ESI/1.0"',


    return $response;

$app->get('/included', function() {
    $response = new Response('Foo');

    return $response;


If your application doesn’t use ESI, you can disable it to slightly improve the overall performance:

$app->register(new Silex\Provider\HttpCacheServiceProvider(), array(
   'http_cache.cache_dir' => __DIR__.'/cache/',
   'http_cache.esi'       => null,


To help you debug caching issues, set your application debug to true. Symfony automatically adds a X-Symfony-Cache header to each response with useful information about cache hits and misses.

If you are not using the Symfony Session provider, you might want to set the PHP session.cache_limiter setting to an empty value to avoid the default PHP behavior.

Finally, check that your Web server does not override your caching strategy.

For more information, consult the Symfony HTTP Cache documentation.

Website powered by Symfony and Twig, deployed on
The Silex logo is © 2010-2018 Symfony