Varnish Cache

Configure Varnish Cache with the GUI

Learning VCL can be a tricky thing so we have made a GUI that let’s you cache your static assets and even HTML documents without knowing VCL. In the left hand side of your Aperture dashboard there is a section called Quick Config which contains the toggles and inputs to configure Varnish Cache. Configure static asset caching Static asset caching is enabled by default to cache your statics for 6 hours and retain your origin cache control headers for the browser cache. »

How to clear the cache

There are three ways to remove objects from the Varnish Cache : Clear the cache by a particular url. Clearing the entire cache. Fine tuned control of the cache with Varnish Cache ban expressions. Clear a particular URL You can remove particular URLs from the cache by entering the URL and clicking Purge. This form accepts wildcards in the form of *, so entering /images* will purge all URLs starting with /images. »

How to clear the cache using the API

From the management console, click API in the top menu. This will bring you to a UI for all our API routes grouped by category. Scroll through the list, Click Show/Hide on the Proxy group, then click on the POST method ending with state. Here, you’ll see an interface to help build your API call. Enter your account id, application id, environment name, and proxy name.These can be obtained from the URL in the management console (go to your aperture homepage and look at the URL - the numbers go accountId -> applicationId -> environmentId). »

Process ESI Directives in JSON responses

If you use Varnish Cache for Content composition using Edge Side Includes you may need to configure Varnish Cache to process ESI directives in files that don’t look like XML. For example, if you are using ESI in an AJAX call that returns some JSON, you might need to enable disable Varnish’s XML check. To do this: Create a file in the varnish directory named proxy-features.json. Add the following content: { "feature/esi_disable_xml_check": true } . »

Serve stale content while the backend is offline

Configuring Varnish Cache to serve stale content is very useful for when your origin crashes. This behavior is achievable when running Varnish Cache as a reverse proxy within the’s Content Delivery Grid. Prerequisites Make sure you have an account on, and have selected Varnish Cache to run in your proxy stack. Note: This guide will be using VCL 4 syntax, so if you are interested in VCL 3 syntax please reach out to us at support@section. »