Re: [whatwg/fetch] HTTP cache partitioning (#943)

@shivanigithub commented on this pull request.



> + <var>topLevelOrigin</var> to <var>request</var>'s <a for=request>client</a>'s
+ <a for="environment">top-level origin</a>.
+
+ <li><p>Otherwise, return null.
+
+ <li><p>Assert: <var>topLevelOrigin</var> is an <a for=/>origin</a>.
+
+ <li><p>Let <var>topLevelSite</var> be the result of <a lt="obtain a site">obtaining a site</a>,
+ given <var>topLevelOrigin</var>.
+
+ <li>
+  <p>Return the HTTP cache associated with <var>topLevelSite</var> and, possibly, a second key.
+  [[!HTTP-CACHING]]
+
+  <p class=XXX>The second key is intentionally a little vague as the finer points are still
+  evolving. See <a href=https://github.com/whatwg/fetch/issues/904>issue #904</a>.

Do you mean the shivanigithub/http-cache-partitioning#2 issue to be ported to a new issue in https://privacycg.github.io/storage-partitioning/ ? I think this plan sounds good.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/943#discussion_r436005921