- From: Roy T. Fielding <notifications@github.com>
- Date: Wed, 21 Dec 2022 10:13:11 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 21 December 2022 18:13:23 UTC
Look at the example for range-set: - The first, middle, and last 1000 bytes: bytes= 0-999, 4500-5499, -1000 That's why it has been implemented differently. The ABNF does not allow a SP after = but one of the examples used a space after the bytes= so that's what people implement. That's an errata. Probably the right fix is [ranges-specifier](https://httpwg.org/specs/rfc9110.html#rule.ranges-specifier) = [range-unit](https://httpwg.org/specs/rfc9110.html#range.units) "=" OWS [range-set](https://httpwg.org/specs/rfc9110.html#rule.ranges-specifier) though we'd probably have to check other servers to see if any fail on OWS there. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1070#issuecomment-1361800123 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1070/1361800123@github.com>
Received on Wednesday, 21 December 2022 18:13:23 UTC