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

@shivanigithub commented on this pull request.



> @@ -2050,6 +2050,34 @@ clearly stipulates that <a>connections</a> are keyed on
      WebSocket saner -->
 
 
+<h3 id=http-cache-partitions>HTTP cache partitions</h3>
+
+<p>To
+<dfn lt="determine the HTTP cache partition|determining the HTTP cache partition">determine the HTTP cache partition</dfn>,
+given <var>request</var>, run these steps:
+
+<ol>
+ <li><p>If <var>request</var> is a <a>navigation request</a>, set <var>environmentSettings</var> to
+ <var>request</var>'s <a for="environment">target browsing context</a>'s <a>active document</a>'s
+ <a>environment settings object</a>. Otherwise let <var>environmentSettings</var> be
+ <var>request</var>'s <a for=request>client</a>.

Added the request's reserved client.
Regarding using the creation URL's origin, in case of iframe, that will not give the top-level origin, right and we want the top-level origin as the partitioning key for an iframe navigation request

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