3 ms·

HTTP caching is a mess. I wonder why no one proposed a properly redesigned and negotiable protocol that covers all the edge cases. (And maybe supports partial c

by romaniv 10y ago

HTTP caching is a mess. I wonder why no one proposed a properly redesigned and negotiable protocol that covers all the edge cases. (And maybe supports partial caching/partial re-validation of pages.)

bhldr 10y ago
On my phone, so unfortunately no reference, but there is a HTTP 2 spec underway that allows a client to send a cache manifest frame. A server can then push the resources that are newer. Pretty much exactly what's needed.
- romaniv 10y ago
  Unless we're talking about different things, cache manifest is an HTML 5 feature designed to enable websites to work offline. That's quite different from HTTP-level caching, which would be applicable to any files/resources and designed primarily with performance and bandwidth savings in mind. I might be unaware of some relevant HTTP 2 features, though.
  - bhldr 10y ago
    Definitely a different thing. This is a HTTP 2 frame, sent by a client
    - romaniv 10y ago
      Could you post a link to the relevant part of the spec or some article dealing with this feature?
pornel 10y ago
The current HTTP RFC is actually quite nice: http://httpwg.org/specs/rfc7234.html http://httpwg.org/specs/rfc7234.html