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

MattMenke2 left a comment (whatwg/fetch#1035)

I think it's worth noting that the connection layers of Chrome's network stack are keyed only on top-level site + is-cross-origin.  Chrome also has a nonce used in some cases (fenced frames) that disables caching and partitions the connection layers as well, and it's introducing another enum for certain cases where requests need to be isolated, but we still want them cached to disk (Currently targeted at the new federated login APIs, which I can't remember the name of, and certain Protected Audiences fetches).  The enum will apply to connections and the HTTP disk cache.

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

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