Chrome does not obey cache headers on refresh, I think they assume something is wrong if you are hitting the refresh button and fetch all files from the server.

I can't really blame firefox for obeying the headers that the server sent them.

This problem hit me very hard, chrome ignores most headers if a server sends a 304 response for a resource.

For a site I was working on, we issued a change to our CSP headers only to attempt to fix a CSP issue that made it to production, and chrome would not accept the new CSP changes since the HTML body and scripts were unchanged.

Had to include the hash of our headers as an HTML comment to allow this dynamic change to be picked up by chrome.