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

I talked with @annevk at [IRC](https://freenode.logbot.info/whatwg/20191205#c2934009).

- We agreed that the secure context restriction is a must-have.
- I misunderstood the motivation for the H2 restriction. I thought the main motivation was for security and that was why I proposed the new header on CORS preflight.
- @annevk pointed out that for some user agents don't want to implement chunked encoding from implementation cost point of view.
- @annevk and I agreed that it's not clear whether we __need__ the new headers from security point of view.

@ddragana, can you tell us Firefox's implementation status of chunked encoding? If it's not there is it very hard to implement it?

I also would like to know, If some user agents don't want to support H1.1 with streaming upload do we actually need H2 restriction? Alternatively we can expose the support status and/or error status to web developers so that they can fall back.




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