- From: Andrew Williams <notifications@github.com>
- Date: Thu, 21 Nov 2024 19:42:52 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/1783/review/2453248742@github.com>
@recvfrom commented on this pull request. > @@ -3133,6 +3133,32 @@ or an <a>implementation-defined</a> value. </div> +<h3 id=storage-keys-for-requests>Storage keys for requests</h3> + +<p class=note>Requests made to Blob URLs (other than those corresponding to navigations) are +prevented from succeeding if the <a spec=storage>storage key</a> of the +<a>environment settings object</a> making the request is different than the +<a spec=storage>storage key</a> of the <a>environment settings object</a> corresponding to where +the Blob URL was created. I was thinking this would make sense in the Infrastructure section like how the `HTTP cache partitioning` section and `determine the HTTP cache partition` algorithm are, but I've moved the algorithm under the `Scheme fetch` section now (and removed the note since it seems kinda out of place now. WDYT? > @@ -4978,6 +5004,29 @@ steps: <p class=note>The `<code>GET</code>` <a for=/>method</a> restriction serves no useful purpose other than being interoperable. + <li> + <p>Let <var>blobStorageKey</var> be the result of running + <a>obtain a storage key for non-storage purposes</a> with <var>blobURLEntry</var>'s + <a>environment settings object</a>. ah yes thanks for pointing this out. Changed -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1783#discussion_r1853233836 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1783/review/2453248742@github.com>
Received on Friday, 22 November 2024 03:42:55 UTC