RFC 7233, "Hypertext Transfer Protocol (HTTP/1.1): Range Requests", June 2014

Note: This RFC has been obsoleted by RFC 9110

Errata ID: 5620
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Armin Abfalterer
Date Reported: 2019-02-01
Held for Document Update by: Barry Leiba
Date Held: 2020-11-13

Section 4.2 says:

Content-Range       = byte-content-range
                    / other-content-range

other-content-range = other-range-unit SP other-range-resp
other-range-resp    = *CHAR

Notes:

Due to the loose definition of "other-content-range" invalid "byte content range" values are possible.

For example, following invalid header value is not valid according to "byte-content-range" (as "complete-length" or "*" is missing) but is yet allowed by "other-content-range".

Content-Range: bytes 42-1233/

The problem might be solved by excluding "bytes-unit" in "other-range-unit".

Report New Errata