Re: [whatwg/fetch] simple range header value parser does not allow for suffix-byte-range-spec (Issue #1450)

Thanks for the info!

> My intent was to be cautious, and only allow stuff browsers already send. If browsers already send this, or a browser wants to start sending this (and folks are confident it's safe to do so), then it makes sense to update the spec.

This makes a lot of sense, especially since all suffix-byte-range-spec ranges can be represented with a byte-range-spec.

> Do browsers ever send a header in that format?

Not that I know of. I opened this issue as I started looking into working on blob range requests (https://github.com/whatwg/fetch/issues/1070). In which, we intend to re-use the single range header parser to also parse the range for the blob request. Once blob range requests are supported, a user could use a suffix-byte-range-spec to attempt to slice the blob. We don't have to support this case (just like we don't support multiple ranges).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1450#issuecomment-1151080179
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1450/1151080179@github.com>