- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Thu, 12 Nov 2020 17:13:18 -0800 (PST)
- To: a.abfalterer@gmail.com, fielding@gbiv.com, ylafon@w3.org, julian.reschke@greenbytes.de
- Cc: barryleiba@computer.org, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been held for document update
for RFC7233, "Hypertext Transfer Protocol (HTTP/1.1): Range Requests".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5620
--------------------------------------
Status: Held for Document Update
Type: Technical
Reported by: Armin Abfalterer <a.abfalterer@gmail.com>
Date Reported: 2019-02-01
Held by: Barry Leiba (IESG)
Section: 4.2
Original Text
-------------
Content-Range = byte-content-range
/ other-content-range
other-content-range = other-range-unit SP other-range-resp
other-range-resp = *CHAR
Corrected Text
--------------
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".
--------------------------------------
RFC7233 (draft-ietf-httpbis-p5-range-26)
--------------------------------------
Title : Hypertext Transfer Protocol (HTTP/1.1): Range Requests
Publication Date : June 2014
Author(s) : R. Fielding, Ed., Y. Lafon, Ed., J. Reschke, Ed.
Category : PROPOSED STANDARD
Source : Hypertext Transfer Protocol Bis APP
Area : Applications
Stream : IETF
Verifying Party : IESG
Received on Friday, 13 November 2020 01:13:41 UTC