Nuxt re-deploy causes payload 404 not found

[gabrielsze]

I believe this was asked here a while back, so it's highly similar.

https://stackoverflow.com/questions/65577842/nuxt-js-app-redeploy-causes-payload-js-404-not-found

Essentially what happens is that on redeploy, there seem to be new payload.js files being loaded up, and those on the site which hasn't been updated cause a 404.

I have the same suspicions it has to do with some caching or the need to flush a new change to users on the "old static sites with old payload". Is there any way to work around such an issue?

[kissu]

Hi, it would probably be interesting where this one do happen, with which configuration, if it still happens while in a private window and if the build is okay locally. Or any relevant info at all actually.

[gabrielsze]

Hey @kissu, I spent some time looking into it deeper, and I suspect it could be due to some form of cache-control. You would notice in the screenshot that the payload seems to be cached for 4 hours - could this be an issue why there's a 404 error whenever there is a redeploy (new payloadjs)? This is on my production site so the error 404 pops up quite often (due to payload 404) and reloading it will definitely solve the issue.

I don't seem to be explicitly setting the cache control of payloadjs so i need to look into it. Could be firebase default though (?)

[gabrielsze]

Seem to have found cloudflare caching my files for 4 hours, which matches the time. Should I be disabling caching for payload.js files?