Follow

What Files and Extensions Does Distil Automatically Cache?

In cloud deployments, you can take full control of how Distil caches your content on our CDN, which is powered by Verizon’s Edgecast network. When Content Caching is enabled, Distil caches and serves your content to help improve your site’s performance.

Our CDN caches based on a list of file extensions. Our CDN will always cache responses for the following extensions:

  • .bmp
  • .class
  • .css
  • .csv
  • .doc
  • .docx
  • .ejs
  • .eot
  • .eps
  • .gif
  • .ico
  • .jar
  • .jpeg
  • .jpg
  • .js
  • .mid
  • .midi
  • .otf
  • .pdf
  • .pict
  • .pls
  • .png
  • .ppt
  • .pptx
  • .ps
  • .svg
  • .svgz
  • .swf
  • .tif
  • .tiff
  • .ttf
  • .webp
  • .woff
  • .woff2
  • .xls
  • .xlsx

NOTE: Distil respects any caching policy headers you have in place. For example, if the response from the origin server contains a Cache-Control header that says "no-cache", then the CDN will honor that and the response will not be cached. If Cache-Control says "max-age=12345", then the CDN will cache the response for 12345 seconds. For more information on using cache control header, refer to the article Cache Policy Headers.

There are certain responses that are not cached by Distil edge nodes - they are ones that have a Content-Type header matching one of the below:

  • video*
  • audio*
  • application/octet-stream
  • application/x-rar-compressed
  • application/zip
  • application/gzip
  • application/x-gzip
  • application/x-gtar
  • application/pdf


NOTE: The asterisks (*) denote wildcards that include any MIME type beginning with the letters "audio" or "video."

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments