Changed resources are still "cached"
Site: https://projectlombok.pages.dev/
I've updated
/js/supporters.js
The generated response headers say cache-control: public, max-age=14400, must-revalidate
My old page does have a different generated etag
But I still get the old version. However, if I add ?foo to the url, I do get the new version. Also the build log says it has updated this file.
My _headers does not contain any cache related entries.
Any idea what's going on?1 Reply
Well, in the meantime the max-age has already passed, my immediate problem is gone, however, I'd like to know how I can prevent this problem in the future.