-
DescriptionWhen updating page data and deploying the changes on netlify, the client only registers the changes when the page is reloaded a second time - even multiple days after the update. Steps to reproduce
Expected resultChanged Content should be immediately visible Actual resultChanges are only visible after explicit page reload EnvironmentRun
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Page data should never be cached. Can you show the |
Beta Was this translation helpful? Give feedback.
-
You can try validating your cache-control headers with https://www.npmjs.com/package/check-gatsby-caching |
Beta Was this translation helpful? Give feedback.
-
@herecydev thank you for pointing this out, my mistake was to not install gatsby-plugin-netlify.
|
Beta Was this translation helpful? Give feedback.
@herecydev thank you for pointing this out, my mistake was to not install gatsby-plugin-netlify.
_headers
file now looks like this, should work, I hope