3 ms·
This is what worries me about the HTTP "Cache-Control: immutable" proposal. Immmutable caching should come with a reliable way to be sure that the content that
by kozak 10y ago
This is what worries me about the HTTP "Cache-Control: immutable" proposal. Immmutable caching should come with a reliable way to be sure that the content that is going to become immutable is not corrupted in the first place.
- fivesigma 10y agoNot if it's over HTTPS, since it guarantees data integrity. Corrupted network bits will cause the connection to fail. If the file is corrupted at the edge server an SRI attribute [1] can detect it, although it's not supported on IE and Safari yet. [1] https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
- m_eiman 10y agoBetter hope the file isn't corrupted while it's being written to disk (or while read, or in place, or…). IMHO, anything immutable should be identified with its SHA2+ hash.
- NKCSS 10y agoDoesn't a CTRL-F5 force a refresh of all resources? That's always an option (although not one non-technical users will know).
- kozak 10y agoYep, a non-technical user will rather go buy a new computer than press Ctrl+F5.