diff --git a/book/http_cache.rst b/book/http_cache.rst index ffb8a1f6636..a902861dcc0 100644 --- a/book/http_cache.rst +++ b/book/http_cache.rst @@ -795,13 +795,13 @@ Gateway caches are a great way to make your website perform better. But they have one limitation: they can only cache whole pages. If you can't cache whole pages or if parts of a page has "more" dynamic parts, you are out of luck. Fortunately, Symfony2 provides a solution for these cases, based on a -technology called `ESI`_, or Edge Side Includes. Akamaï wrote this specification +technology called `ESI`_, or Edge Side Includes. Akamai wrote this specification almost 10 years ago, and it allows specific parts of a page to have a different caching strategy than the main page. The ESI specification describes tags you can embed in your pages to communicate with the gateway cache. Only one tag is implemented in Symfony2, ``include``, -as this is the only useful one outside of Akamaï context: +as this is the only useful one outside of Akamai context: .. code-block:: html @@ -936,7 +936,7 @@ used ``render``. .. note:: - Symfony2 detects if a gateway cache supports ESI via another Akamaï + Symfony2 detects if a gateway cache supports ESI via another Akamai specification that is supported out of the box by the Symfony2 reverse proxy. diff --git a/cookbook/cache/varnish.rst b/cookbook/cache/varnish.rst index e72612acff6..48eb43c2592 100644 --- a/cookbook/cache/varnish.rst +++ b/cookbook/cache/varnish.rst @@ -19,7 +19,7 @@ As seen previously, Symfony2 is smart enough to detect whether it talks to a reverse proxy that understands ESI or not. It works out of the box when you use the Symfony2 reverse proxy, but you need a special configuration to make it work with Varnish. Thankfully, Symfony2 relies on yet another standard -written by Akamaï (`Edge Architecture`_), so the configuration tips in this +written by Akamai (`Edge Architecture`_), so the configuration tips in this chapter can be useful even if you don't use Symfony2. .. note::