Re: [fetch] Support full-duplex HTTP streaming (#229)

So another problem here is that step 17 of main fetch assumes that by the time we receive a response (all its headers, not necessarily the body), the request has been fully transmitted. It's important that step 17 does not do that notification earlier (due to redirects), but we could maybe change it to do it later. We'd have to figure out what an acceptable signal would be for doing it later (that is, what fully transmitted means in this new world).

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/229#issuecomment-191754802