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

annevk commented on this pull request.



> +  <p>If <var>request</var>'s <a for=request>client</a> is null, terminate these steps.</li>
+
+ <li>
+  <p>Let <var>environmentSettings</var> be <var>request</var>'s <a for=request>client</a>.</li>
+
+ <li>
+  <p>Let <var>topLevelOrigin</var> be <var>environmentSettings</var>'s top-level origin and
+  <var>origin</var> be <var>environmentSettings</var>'s origin.</li>
+
+ <li>
+  <p>Return the HTTP cache associated with <var>topLevelOrigin</var> and optionally,
+  <var>origin</var>.</li>
+</ol>
+
+<p class="note no-backref">User agents can use the registrable domains associated with
+<var>topLevelOrigin</var> and <var>origin</var> instead of the origins themselves.

We are reconsidering "site" (aka "agent cluster key" https://html.spec.whatwg.org/#obtain-agent-cluster-key) based on Chrome's feedback. Additionally Chrome's triple-keying made us reconsider omni-keying (each parent up to the top-level adds a key), but it's still early days in proving it's feasible.

-- 
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_r380299129