[whatwg/fetch] Add support for parsing a suffix byte range spec (PR #1454)

Add support for parsing a range header in the suffix byte range spec
form.

<!--
Thank you for contributing to the Fetch Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
-->

- [ ] At least two implementers are interested (and none opposed):
   * …
   * …
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * Partially [here](https://github.com/web-platform-tests/wpt/pull/34384#discussion_r898469534)
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: …
   * Firefox: …
   * Safari: …
   * Deno (not for CORS changes): …

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/1454


-- Commit Summary --

  * Add support for parsing a suffix byte range spec

-- File Changes --

    M fetch.bs (16)

-- Patch Links --

https://github.com/whatwg/fetch/pull/1454.patch

https://github.com/whatwg/fetch/pull/1454.diff


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1454

You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1454@github.com>