- From: valadaptive <notifications@github.com>
- Date: Mon, 18 Aug 2025 20:00:30 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 August 2025 03:00:34 UTC
valadaptive left a comment (whatwg/fetch#1850) > Would the effect of this change be to disallow content encodings from being requested on range requests from Fetch? > > If so that's a constraint on how applications use HTTP. Experience shows that would be a significant impediment to deployment, so the tradeoff should be carefully examined: is it worth constraining the protocol's use to promote interoperability with a set of buggy servers? Specifically, how large is that set, and how current is our information about it? Content encodings are currently disallowed from being requested on *any* request. `Accept-Encoding` is a forbidden request-header. The change proposed here shouldn't affect behavior at all. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1850#issuecomment-3199045324 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1850/3199045324@github.com>
Received on Tuesday, 19 August 2025 03:00:34 UTC