MarkBennett
commented
10 months ago For anyone else seeing this, we found that adding the following to our gatsby-config.ts ensured that our html and page-data had the correct cache control, even when Netlify configuration changed.
{
resolve: `gatsby-plugin-netlify`,
options: {
// Apply recommended Gatsby caching headers to Netlify's CDN
// See: https://www.gatsbyjs.com/docs/how-to/previews-deploys-hosting/caching/
headers: {
"/*.html": ["Cache-Control: public, max-age=0, must-revalidate"],
"/page-data/*": ["Cache-Control: public, max-age=0, must-revalidate"],
},
},
},
A configuration issue with Netlify last week caused our Gatsby application to fail rehyrdation as some of the data on our site was using old cached versions.
We eventually traced this back to Netlify serving
Cache-Control: public, max-age=31536000, immutableheaders for html, page-data, and app-data.json on our site. The sw.js was not affected as it's included in the headers defined by this plugin.In order to avoid future configuration changes impacting Gatsby content caching, our team would like to propose including the html, page-data and app-data cache headers recommended by Gatsby in their Caching Static Site documentation be included in the headers generated by this plugin, so that future Netlify configuration changes don't affect Gatsby sites like ours was.
Happy to contribute a PR but wanted to reach out to understand the appetite and if there are issues we're not aware of.
We can confirm that even the latest version of this plugin does not generate the cache control headers recommended in the Gatsby docs. I've included a sample generated using gatsby-plugin-netlify v5.1.0:
_headers