Browser doesn't cache images despite cache header when html is not cached

Question

I'm caching our generated images using the HTTP header "Cache-Control", however, when I don't cache the HTML file (comprising those img tags) using "no-cache" I see further requests sent to the server (as I add, remove, and re-add those tags). Caching the HTML file results in cached images (and no further requests).
The Only similar case I could find is this.
Any lead/link will be appreciated.

Browser: Version 32.0.1661.0 canary Aura
p.s. I very much prefer keeping the HTML file not cached.

If you check in the web server log, is it sending an HTTP status code of 304, i.e. "Not modified"? If so, the server will not be re-sending the image. — Andrew Morton
– Andrew Morton, Commented Oct 13, 2013 at 17:12
For Chrome, 200 OK doesn't necessarily mean the request ever left the client. In many cases the response is a re-transmit of the cached version and never hits the server. The status will be 200, which makes sense, but the status message would be OK (not 'cached') which drove me crazy at some point. The only distinctions I could find between these responses and actual responses were: a missing Connection header (which otherwise is almost always present) and a Date header with a value preceding the request sent. Are your requests actually hitting the server? — Ophir Radnitz
– Ophir Radnitz, Commented Oct 13, 2013 at 18:50

shex · Accepted Answer · 2013-10-14 09:12:02Z

6

Eugene Olshenbaum answered on twitter: "close developer tools, when it is open, chrome ignores headers :))" The cache was "disabled" while the dev tools were open. Not sure why I didn't see any calls to the server if the HTML file was cached.

answered Oct 14, 2013 at 9:12

shex

3565 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

i-CONICA Over a year ago

This. Even though "disable caching" wasn't ticked, I wasn't seeing any resources loading "from cache", and had a high TTFB. Closing the dev tools inspector then caused images to load instantly, from cache. Seems cache control headers are ignored.

Collectives™ on Stack Overflow

Browser doesn't cache images despite cache header when html is not cached

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related