You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
What is the issue with the Fetch Standard?
Range
requests are critical in media streaming applications, and I believe they should be safe for no-cors mode. I would like them to be added to the list of no-cors safelisted headers: https://fetch.spec.whatwg.org/#no-cors-safelisted-request-header-nameSee conversation in #1310.
The text was updated successfully, but these errors were encountered: