The information in this article only applies to CrowdHandler DNS integrations created after 07-08-2024. For DNS integrations created before this date, if you would like more information on default pattern exclusions and how they are cached, please contact support@crowdhandler.com

At the time of writing (see the CrowdHandler control panel for an up to date list), requests containing the following file type extensions are not checked by CrowdHandler's queueing mechanic. 

.css, .ico, .jpg, .jpeg, .js, .otf, .png, .svg, .tff, .webp, .woff, .woff2

Requests with these file types are cached by default for 300 seconds. You can alter the caching behaviour by setting cache-control response headers to the relevant assets.

  1. When your origin server provides `Cache-Control` or `Expires` headers, CloudFront will use these to cache your content according to the specified time (e.g., `Cache-Control: max-age=3600` caches for 1 hour). 
  2. If no cache headers are set, CloudFront will default to caching the content for 300 seconds (5 minutes). This setting balances performance with fresh content delivery for assets that don’t specify a caching duration.
  3. To prevent caching entirely, set `Cache-Control: no-cache, no-store, must-revalidate` and `Expires` to a past date (e.g., `Expires: Thu, 01 Jan 1970 00:00:00 GMT`). With our minimum TTL of 0, CloudFront will bypass caching and retrieve fresh content from your origin every time.