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

> Having an API that only works over H/2, which does not require the
complexities previously described and deterministically fails fast, seems a
much better developer experience than a non-deterministic API that
heuristically encounters issues. 

The same argument goes with the H/2 restriction, as the app doesn't control what forward proxies the client will interact with and not all forward proxies support H/2.  

OTOH, H/1 proxies should support chunked T-E (*), and for servers that have issues with chunked T-E, the app (or client libraries for the end-points) would know not to use request streaming.



-- 
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-588571444