3 ms·
Why would a browser cache an incomplete response? Content-Length exists, and failing that, there are chunked transfers.
by minitech 10y ago
Why 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.