4 ms·
OK So the Expires header is set to 15 minutes in the future. I think this is the secret sauce. I've never seen this before but I plan on trying it out heavily i
by triangleman 6y ago
OK So the Expires header is set to 15 minutes in the future. I think this is the secret sauce. I've never seen this before but I plan on trying it out heavily in the future. You don't even need to wait for a 304 content not modified, there's simply no request at all. So cool!
edit: It seems like Expires is a bit older than cache-control, so not as relevant as I thought. I'm not seeing the 365 day cache control header you listed, it's anywhere from 5 minutes to 30 minutes.
It's just weird to see a browser totally trust a cache and not even verify using "etag" or otherwise. I'll probably have to do a lot of trial and error to get this to happen but I really like it, because it feels so fast.
- segfaultbuserr 6y agoLook carefully, it's not 15 minutes, but an entire year, it expires in 2021. Nevertheless, any time in the future should work.
- triangleman 6y agoI mean look at the MDN page on cache control itself: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ca... Now click away and click back. There will be a request and a 304. That's what I'm used to, not an instantaneous non-request.