3 ms·
The problem is that browsers didn't do the right thing, and now they can't do the right thing because web developers relied on actual browser behavior rather th
by klodolph 10y ago
The problem is that browsers didn't do the right thing, and now they can't do the right thing because web developers relied on actual browser behavior rather than idealized spec-compliant behavior. If you've heard that story before, it's because a dozen other minor warts (especially regarding HTTP headers) appeared for the exact same reason.
- Groxx 10y agoWell... kinda. I'd say this is the result of a mismatch between "refresh everything, anything could have changed" and what most people actually want when refreshing, which is "check for new content". "cache-control: immutable" at least lets servers declare a contract that pushes those two closer towards each other, and it also works perfectly for those cache-busting resource-version-params, which browsers haven't been able to trust. Which is probably why Chrome had that POST-invalidation thing - there are a lot of flawed cache headers out there, and users don't care that you're following the spec when things break.
- klodolph 10y agoYes, and it also had to work (long ago) with poorly-written, non-standards-compliant HTTP proxies.