Hi, I am having an issue that I believe is caused by the Headers on my site, but I can’t seem to figure out the issue. When I initially load the site, I am shown an old version. After using clear cache and reload in Chrome the correct version is shown. Then if I reload again it shows the old version…

Hi, @Blake32p . I also notice that this site is using a service worker: [image] [Support Guide] Understanding & unregistering service workers Support Guides Last reviewed by Netlify Support - August, 2023 A service worker is a script that your browser runs in the backgrou…

hi there, first questions: are you sure you are adding the changed files to the repo and pushing them to git? have you checked your deploy history and things are deploying building correctly? I am seeing some errors in the javascript console when I load that site.

Hi, thanks for the quick reply. I can confirm that my repo looks correct, the items is deploying from Master and I can push changes to it and have them show up correctly on the site - when the correct version is displaying. There are some javascript error, the site is very much a work in progress, b…

hmm - i have clicked around a bit, and the only version i am seeing is with a black menu. [image] how does it look when you access from an incognito window or a different browser?

hmm maybe its just an issue with my computer. Safari shows me the incorrect site, as does Chrome. But Chrome in incognito shows the correct site. Safari on my phone also shows the correct site. Firefox just shows me a white screen…not sure what’s up with that.

The problem initially started when I was trying to use a webfont and getting a 403 error, I think the error was that the header didn’t have a cross-origin referrer. So I tried some of the things mentioned in this post . I’m not sure if something I did there with changing cache-control could cause an …

Hi @Blake32p , I see you have custom cache-control headers set and those are most likely what’s causing the issue. I recommend letting us handle caching for you and see if you have a better experience. You can do this by removing the cache control headers you’re sending your deploy then wiping the ca…

That was it! I didn’t realize I had to unregister the service worker. I followed the instructions here on removing the service worker and that solved my issue. Thanks so much!

Old version of website shown, what could cause this?

Support

Blake32p November 11, 2019, 2:11pm 8

Hi Gerald, thank you for replying to my post. I removed the netlify.toml that had the custom headers. Is that enough to reset the settings so Netlify can handle the cache? Also I added the code back in that has the 403 issue.

CDN asset caching problem after deployment

Topic		Replies	Views
Netlify serve old cached version Support building , deployment , caching	41	7256	March 29, 2022
Netlify + Gatsby serves old/cached (pre-Gatsby) version of site Support building , deployment , gatsby	13	4277	October 30, 2020
Cached version of website not updating on new build/repo change Support deployment	6	3336	December 28, 2020
CDN asset caching problem after deployment Support netlify-cdn-adn	12	4825	June 3, 2020
Cache issue - old version being served to the users Support deployment , nextjs	5	557	June 17, 2023

Old version of website shown, what could cause this?

Related topics