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

> How is the flag different from checking for such a header and the mode being "no-cors"?

Right now the flag allows the headers to be carried over when calling `new Request(request)`, but I'll see if I can remove the need for it.

> The response side also needs changes right, to indicate that it was range-requested and such?

Yeah, I'm doing that next.

-- 
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#issuecomment-378635644