3 ms·
With WiFi hotspots dropping connections more often than not, how many people would know they need to CTRL-F5 to "fix" a broken page/image/JS/CSS? I just hope t
by jjoe 10y ago
With WiFi hotspots dropping connections more often than not, how many people would know they need to CTRL-F5 to "fix" a broken page/image/JS/CSS?
I just hope the draft as-is expires and never makes it to an RFC.
- minitech 10y agoWhy would a browser cache an incomplete response? Content-Length exists, and failing that, there are chunked transfers.
- jjoe 10y agoContent-Length MUST be ignored in some cases (encoding). Not all send a Content-Length header (it's a SHOULD not a MUST).
- minitech 10y agoIf you don’t tell the browser in some way where your response ends (with Content-Length, chunked, or HTTP/2 [?]), you can’t reuse connections, as far as I know. If that’s the case, you probably don’t care enough about performance to use `immutable` anyway.
- jjoe 10y agoJust playing devil's advocate there for a minute. And this is definitely one of those things I've had to work around.
- twoodfin 10y agoCould you clarify your objection? Presumably clients would never immutably cache a resource they couldn't validate.
- jjoe 10y agoHow does validation work in the case of a 200 status and no Content-Length header?
- scrollaway 10y agoI'd also like to know. I hope subresource integrity can be implemented alongside the cache control and prevent caching a bad file. https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity https://developer.mozilla.org/en-US/docs/Web/Security/Subres...