- From: Brad Isbell <notifications@github.com>
- Date: Tue, 19 Nov 2019 20:57:15 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 20 November 2019 04:57:17 UTC
Are there more details about the reasoning behind the proposed restrictions? Streamed HTTP PUT requests are made all the time. Many of these likely violate spec by not using chunked encoding but also not specifying content length (in the case of indefinite lengths, like live streaming media). Some do successfully use chunked encoding, but I don't have a sense for how widespread this is. In any case, it seems strange to limit what the browser can do out of a sort of protection for a server. I don't understand the reason for a server to declare that it supports chunked encoding from the client. Is there a particular potential side effect that is the source for concern? -- 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-555837906
Received on Wednesday, 20 November 2019 04:57:17 UTC