[whatwg/fetch] Allow range header to be set by APIs (#560)

This is part of #144.

The aim is to allow APIs to use the range header for no-cors requests, and allow them to pass through a service worker, but disallow modification of these requests, and disallow developers creating their own no-cors ranged requests.
You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/560

-- Commit Summary --

  * This isn't true, it's used for fetch responses too.
  * Adding concept
  * Allow range header to be set by APIs, but remove it if the developer modifies the request.
  * Disallow ranged responses for non-range request. Disallow opaque ranged responses to be used for other requests.

-- File Changes --

    M fetch.bs (78)

-- Patch Links --

https://github.com/whatwg/fetch/pull/560.patch
https://github.com/whatwg/fetch/pull/560.diff

-- 
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/pull/560