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

That sounds somewhat reasonable for the request side. How is the flag different from checking for such a header and the mode being "no-cors"?

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

-- 
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-378625462

Received on Wednesday, 4 April 2018 14:45:25 UTC