Caching and purging
For caching, we need to consider the interactions between the browser’s cache, network latency, HTTP/2 Push, and even some browser bugs. This is why configuring caching correctly is no small feat.
ShimmerCat ships with sane defaults for static asset caching. They “just work”, but there are of course ways of tuning the cache behavior and customize them whatever way you want.
ShimmerCat caches static assets at the edge servers to improve loading times for your customers. When you update your static assets you therefore need to notify the edges of new versions of the files. By clearing cached files you force ShimmerCat to fetch a fresh version of those files from your origin server.