1 reply

Changed resources are still "cached"

/js/supporters.js

/js/supporters.js

The generated response headers say

cache-control: public, max-age=14400, must-revalidate

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

?foo

to the url, I do get the new version. Also the build log says it has updated this file.

My

_headers

_headers

does not contain any cache related entries.

Any idea what's going on?