- From: Brad Isbell <notifications@github.com>
- Date: Tue, 10 May 2022 09:58:27 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/425/c1122646961@github.com>
> FWIW gRPC/web was the only web developer who wanted to use this feature with HTTP/1.1, so I believe we all are now happy to drop the support of this feature on HTTP/1.1. I had no idea this was available on HTTP/1.1... we've been needing this for streaming media for a very long time, and yet previous discussions stated that it was locked to HTTP/2. Existing servers, such as Icecast and FFmpeg, do not support HTTP/2 and have no need to. They also do not necessarily need to support HTTPS. I would strongly urge reconsidering. Please keep HTTP/1.1 streaming request bodies available, and *tell us how to use them in Chromium**. It does not seem to be available with current builds. If there is some sort of flag we need, what is it? And then, we should go back to all of the threads where this was discussed and inform folks that it is available: - https://groups.google.com/a/chromium.org/g/blink-network-dev/c/bsVgOxNCzFc - https://stackoverflow.com/a/41222366/362536 - https://github.com/whatwg/fetch/issues/966 - https://stackoverflow.com/q/35899536/362536 - https://github.com/whatwg/fetch/issues/439 - https://github.com/whatwg/fetch/issues/88 -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/425#issuecomment-1122646961 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/425/c1122646961@github.com>
Received on Tuesday, 10 May 2022 16:58:39 UTC