Issue metadata
Sign in to add a comment
|
Launch bug for StaleWhileRevalidate |
||||||||||||||||||||||||||||||||||||||||||
Issue descriptionFiling a formal OWP launch tracking for SWR (intent to implement/ship, privacy, security and test reviews already done a while ago) Change description: Stale-while-revalidate is a cache-control extension which enables a resource to be used immediately from the cache while it is revalidated against the origin web server in the background. See https://docs.google.com/document/d/1izgyCOcRtz5Kc0rFtZ68p5mj3E__Uvgpf-5cJJHi7jE/edit for more background. Changes to API surface: 1. Support for stale-while-revalidate attribute in HTTP Cache-control header 2. Send back a new header called Resource-freshness to guide developers toward efficient (max-age, s-w-r) pair of values. Links: - https://tools.ietf.org/html/rfc5861 - https://github.com/KenjiBaheux/resource-freshness Support in other browsers: Internet Explorer: no Firefox: no Safari: no Proxies and CDN: supported by a few high profile players. === Plan === M-49~: experimentations - smoketest: canary/dev (Desktop) successful - beta (Android): moot because Uniformity isn't achieved for the metrics we care about with similarly sized but random users population. We would like to expand the experiment to Stable in order to achieve Uniformity and observe meaningful results.
,
Mar 2 2016
,
Mar 2 2016
,
Mar 14 2016
,
Mar 10 2017
[Update on SWR] We've had a behind the flag implementation for a while and did an experiment but haven't been able to ship it due to some tough remaining issues... We believe that these issues are specific to Chrome's current architecture. In particular, problems with redirects and cookies have been noted as serious show-stopper because getting both of these to work correctly would require some major changes to the way the cache interfaces with the rest of Chrome's net layer. Given upcoming major refactors (e.g. PlzNavigate, Servicification of //net) that would be impaired by the current implementation of S-W-R, we have decided to temporarily remove our implementation. We still believe that this primitive has significant potential. Mozilla has an open bug[1] for this feature and we hope that they will be able to ship this primitive soon so that the community can help us better understand its impact and therefore facilitate a proper follow-up in Chrome and hopefully other browsers. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=995651 |
|||||||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||||||||
Comment 1 by kenjibaheux@chromium.org
, Mar 2 2016