Re: [whatwg/fetch] Add Range to no-cors safelisted headers (Issue #1767)

Every time we have expanded what `no-cors` can do we have regretted it. There's also a general policy that new features need to use CORS. This idea has the backing of Chrome's security team? I'm very much opposed to this.

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

Message ID: <whatwg/fetch/issues/1767/2294653885@github.com>

Received on Saturday, 17 August 2024 05:55:50 UTC