Re: [fetch] Developer-controlled streams for request/response (#88)

> On the wire, it just terminates somehow? How does HTTP work?

For H1, you'd just close the connection. For H2, you'd cancel the stream.

> Always do content-encoding: chunked, and do uploads as chunked encoding, which we need to spec in some way

As noted elsewhere, that's not very interoperable with existing, deployed servers; while *some* will accept chunked encoding, *most* will 411 (Length Required) if there's no Content-Length, because they don't want to infinitely buffer the request. 

One way around this would be to specify that if Content-Length is set, you'll only write that many bytes to the wire, and error if it tries to write more. 

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