[whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)

We allow no-cors requests to have `Range` headers as long as it's set by an internal API, and the request is unmodified.

It feels like CORS requests should be able to use `Range` in particular ways without triggering a preflight. If the format matches what https://fetch.spec.whatwg.org/#concept-request-add-range-header can create, that's ok right?

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