- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Thu, 11 Jun 2015 11:49:16 -0700 (PDT)
- To: fielding@gbiv.com, ylafon@w3.org, julian.reschke@greenbytes.de, barryleiba@computer.org, mnot@mnot.net
- Cc: nherring@google.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted for RFC7233, "Hypertext Transfer Protocol (HTTP/1.1): Range Requests". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7233&eid=4391 -------------------------------------- Type: Technical Reported by: Nathan Herring <nherring@google.com> Section: 2.1 Original Text ------------- If a valid byte-range-set includes at least one byte-range-spec with a first-byte-pos that is less than the current length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is satisfiable. Otherwise, the byte-range-set is unsatisfiable. Corrected Text -------------- If a valid byte-range-set includes at least one byte-range-spec with a first-byte-pos that is less than the current length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length and the current length of the representation is non-zero, then the byte-range-set is satisfiable. Otherwise, the byte-range-set is unsatisfiable. Notes ----- Asking for a range that includes trailing bytes (e.g., Range: bytes=-1) when the entity is zero bytes is, as stated here, satisfiable, and yet the service would be forced to yield a 206 code and there is no valid representation of Content-Range header, since you cannot specify a range with no length using the byte range type, the none range type is specified in section 2.3 with a meaning for Accept-Ranges only, and there are no other acceptable ranges in the IANA registry. The alternative would be that we could overload the use of the none range and return 206 with Content-Length: 0, Content-Range: none for these requests for final bytes. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- 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 Thursday, 11 June 2015 18:52:14 UTC