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

Rebased and addressed issues.

I didn't match the CORB sanitising in the end. As you said, it's kinda in a different place. CORB want to replace the response as soon as possible, but I'm doing it really late in the fetch as I need to check against the original request.

I'm a little unsure if I need to be setting *HTTPS state* or not.

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

Received on Thursday, 17 May 2018 17:20:10 UTC