Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

I'm saying that in this state system (and we can say that it'd be only be reflecting the state of the response, ie Step 2 / State B are followed immediately by Step 5 / State E - the request state'd probably be tracked separately, possibly under an `upload` object like how XHR's progress events are factored), the "receiving headers" state would encapsulate *all redirect responses*, to keep redirects properly opaque, and Step 6 would only trigger after the first *non*-redirect response's headers had finished (a la the semantics of XHR's `HEADERS_RECEIVED` readyState).

-- 
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/issues/447#issuecomment-292794240