Re: [whatwg/fetch] Should network state be keyed beyond the top-level site (#1035)

recvfrom left a comment (whatwg/fetch#1035)

To give my understanding of the current state, at least w.r.t. the HTTP cache:
 - Safari partitions by top-level site [1]
 - Firefox partitions by top-level site [2] and an "is-cross-origin-fetch" boolean [3]
 - Chrome partitions by top-level site, frame site, and an "is-iframe-navigation" boolean (and we soon want to launch an "is-cross-site-main-frame-navigation" boolean)

Since the discussion in this thread is a few years old, I was wondering if there might be any new thoughts regarding standardizing HTTP cache partitioning by more than top-level site. WDYT? Is additional keying for the HTTP cache in Safari / Firefox something that is being / might be considered?

Regarding the issue discussed for service worker caching, would it make sense to track that problem in a separate issue?

CC @artines1 @bvandersloot-mozilla

[1] https://webkit.org/tracking-prevention/#partitioned-third-party-http-cache
[2] https://developer.mozilla.org/en-US/docs/Web/Privacy/State_Partitioning#network_partitioning
[3] https://hg.mozilla.org/mozilla-central/rev/94ed4d6361b3



-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1035#issuecomment-2658239821
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1035/2658239821@github.com>