This post (updated recently)
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 …
mentions that Gatsby users should use this to avoid caching issues. The plugin however has been deleted from Github by the author, and I am unsure if this is still safe or relevant. I still get things like this this where each build has a bunch of new assets, and I don’t want the cache to keep changing on our deployed sites.
I think it’s always good to avoid fingerprinting when using Netlify, but here is a relevant discussion:
opened 03:08AM - 09 May 22 UTC
documentation
priority: low
Greetings team 👋
I recently opened up https://answers.netlify.com/t/cdn-site… -content-not-updating-after-gatsby-upload-build/56146/1 after running into some no-fun caching issues on my Gatsby site. After digging into the rabbit hole (as noted in the thread), the long-cache-headers strategy this plugin employs clashes with [`gatsby-plugin-remove-fingerprints`](https://www.gatsbyjs.com/plugins/gatsby-plugin-remove-fingerprints/) — long cache-headers for Gatsby files with no fingerprints makes for a bad time when subsequent builds produce the same named (but not fingerprinted) files 😅
Just wanted to recommend adding a note of incompatibility in the README of this project as to maybe help other folks in the future 🙂