Re: [whatwg/fetch] Request body streams should use chunked encoding (#966)

Browsers don't currently send Transfer-Encoding request headers at all (and servers likely don't support them).  Moreover, without a content-length, the only way for a client to indicate the end of the request is Transfer-Encoding: chunked (which is what we're discussing..) or half-closing the socket.  Browsers don't do the latter (and lot of servers probably wouldn't work if browser did that), and making an API require sockets not be reused if using HTTP/1.x seems not great.

-- 
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/966#issuecomment-614793027