Using Immutable Caching to Speed Up the Web

Re:Using Immutable Caching to Speed Up the Web by romaniv on Thursday January 26, 2017 @02:44PM (#13494594)

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.)

[ Parent | on HN ]

Re:Using Immutable Caching to Speed Up the Web by bhldr on Thursday January 26, 2017 @02:51PM (#13494675)

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.

[ Parent | on HN ]

Re:Using Immutable Caching to Speed Up the Web by romaniv on Thursday January 26, 2017 @03:05PM (#13494811)

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.

[ Parent | on HN ]

Re:Using Immutable Caching to Speed Up the Web by bhldr on Thursday January 26, 2017 @03:15PM (#13494878)

Definitely a different thing. This is a HTTP 2 frame, sent by a client

[ Parent | on HN ]

Re:Using Immutable Caching to Speed Up the Web by romaniv on Thursday January 26, 2017 @03:59PM (#13495203)

Could you post a link to the relevant part of the spec or some article dealing with this feature?

[ Parent | on HN ]

Re:Using Immutable Caching to Speed Up the Web by pornel on Thursday January 26, 2017 @07:04PM (#13496609)

The current HTTP RFC is actually quite nice: http://httpwg.org/specs/rfc7234.html

[ Parent | on HN ]