Luca Casonato

> I agree that it's not desirable to have Request or Response instances that can contain Set-Cookie headers in their Header objects. But only on the web! In server side...

@domenic I did not phrase that very elegantly. What I meant was that there is no value for the web if this change is looked at in total isolation, pretending...

I think this is reasonably established at this point: the bytes of the `ReadableStream` should be the raw bytes on the wire that represent the formdata request. This is also...

@jasnell @kentonv thoughts?

To be clear, I am not explicitly vouching for duplex streams to make it into the initial request body uploading implementation in browsers, I just want to make sure that...

> so if you could elaborate on what prohibits it that would help The promise returned from `fetch` does not resolve until the entire `request.body` ReadableStream has been read and...

> Does the specification also have such issues? As far as I can tell, yes. The request body is sent synchronously before receiving response headers (not in parallel). See the...

One question this brings up: if request body sending on _HTTP-network fetch_ happens in parallel, how and where are errors during request body sending propagated to the user?

Yeah. For users that are using upload streams it can be surfaced as a cancellation of the stream. Maybe the error could be surfaced as a rejection of the promise...

@ricea Some comments: HTTP is not half duplex. It allows for simultaneous request body and response body streaming at a per request level. This is supported in both HTTP/1.1. and...