Re:Using Immutable Caching to Speed Up the Web
by jjoe on Thursday January 26, 2017 @01:53PM
(#13494117)
Meant to say that there's no conditional with immutable. Corrected, thanks.
Re:Using Immutable Caching to Speed Up the Web
by duskwuff on Thursday January 26, 2017 @02:54PM
(#13494696)
I still don't think that's accurate. My experience is that a future Expires date -- even relatively near-future -- is sufficient to prevent an If-Modified-Since request. (Which is what I think you mean by "304 request".)
Re:Using Immutable Caching to Speed Up the Web
by bzbarsky on Thursday January 26, 2017 @03:19PM
(#13494917)
For normal loads, yes.
The problem people are trying to solve here is that users hit the relaod button. A lot. And if you hit the reload button, that will send If-Modified-Since for everything on the page, no matter what Expires says, because the user intent is to ignore Expires headers.
That's what the immutable thing is about: indicating that even in the reload scenario the Expires is authoritative and no If-Modified-Since request should be sent.
Re:Using Immutable Caching to Speed Up the Web
by duskwuff on Thursday January 26, 2017 @06:58PM
(#13496574)
Aha. The forced If-Modified-Since on reload is the piece I was missing. Thanks.
Re:Using Immutable Caching to Speed Up the Web
by jjoe on Thursday January 26, 2017 @03:18PM
(#13494905)
It's up to the client to decide based on Last-Modified (if previously sent by the server) and its own implementation. But I guess browsers are going to be a tad bit aggressive especially if Last-Modified is absent. Hence the overly aggressive 304s.
(Also, "304" is an HTTP response code -- "Not Modified" -- not something the browser sends.)