Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP cache partitioning #943

wants to merge 3 commits into
base: master


Copy link

commented Sep 26, 2019

Adds a section to define the HTTP cache associated with a request as per HTTP cache partitioning.
github issue: #904

Preview | Diff

@shivanigithub shivanigithub marked this pull request as ready for review Sep 26, 2019
<p>A given request has an associated HTTP cache derived from the primary key(s). The primary key
may be the top-frame origin of the document and also possibly the origin of the subframe
associated with the request. When performing an <a>HTTP-network-or-cache fetch</a>, the associated
HTTP cache is used to fetch the request URL.

This comment has been minimized.

Copy link

annevk Sep 27, 2019


I was thinking that we'd do this much more explicit. In particular, update HTML to define and propagate the top-level origin concept appropriately and then whenever we mention HTTP cache in this document instead invoke an algorithm that returns the appropriate cache. With this approach there's a lot of action-at-a-distance which is hard to maintain and often leads to all kinds of subtle issues.

This comment has been minimized.

Copy link

shivanigithub Oct 3, 2019


Sounds good. Created a pull request on the html spec for defining top level origin. PTAL, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.