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

Ok, I've addressed the nits and abstracted creating a "sanitized response". There was a little bit of loop-jumping to do, since CORB deals exclusively in unfiltered responses, and in this PR I'm dealing exclusively with filtered responses.

Since I'm copying cover the CORS/MIX data over anyway, I've moved by range-check before those steps. This makes it a little closer to the CORB steps.

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

Received on Monday, 21 May 2018 10:47:03 UTC