perry
April 10, 2020, 6:36pm
4
well, I’m glad its fixed!
As far as delays go - there isn’t really a way to pinpoint exactly what happened here without something like an x-nf-request-id (more below), because we serve so much traffic that even knowing an approximate time window when the issue occurred barely narrows it down.
It really depends on exactly how your site is set up, also. You can learn a little more about how best to take advantage of caching here:
Last reviewed by Netlify Support - August, 2023
Our CDN derives much of its efficiency from files whose checksums don’t change between deploys.
For instance, in a blog, you usually write or update one article in one file, while the rest of the content remains unchanged. In this typical use case, we don’t need to re-upload and re-process these files, since our CDN already has them stored - no checksums have changed except the one file. This also means that your visitors’ browsers don’t need to …
Last reviewed by Netlify Support on August 2023
While the topic of caching effectively is complex, Netlify’s solution is designed to be automatic and worry-free. It shouldn’t require any special configuration or build tools like cache-busting or service workers to deliver an optimal experience.
atomic rollbacks and deploys , which…
Last reviewed by Netlify Support staff August 2023
1 Like
