RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

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

Note: This RFC has been obsoleted by RFC 9110

Source of RFC: httpbis (wit)

Errata ID: 4358
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Tim
Date Reported: 2015-05-07
Held for Document Update by: Barry Leiba
Date Held: 2015-05-12

Section 4 says:

The 206 (Partial Content) status code indicates that the server is
successfully fulfilling a range request for the target resource by
transferring one or more parts of the selected representation that
correspond to the satisfiable ranges found in the request's Range
header field (Section 3.1).

It should say:

The 206 (Partial Content) status code indicates that the server is
successfully fulfilling a range request for the target resource by
transferring one or more parts of the selected representation that
correspond to the satisfiable ranges found in the request's Range
header field (Section 3.1). A response may chose to satisfy only
part of a requested range.

Notes:

Firefox and Chrome already behave as if the "Corrected Text"
statement is true.

It may be desirable if for example a user returns to a
html5 video with auto play, pauses the video and is only
interested in responding to a comment on the page. In this example
it would be unnecessarily costly to transfer the whole 128GB when
the user only consumes a few MB.

Alternative: maybe it should only be true if last-byte-pos is
absent.

----- Verifier Notes -----
The reporter is uncertain of the meaning and asks that it be clarified, one way or the other. A future update of the document might consider clarifying wording.

Report New Errata



Advanced Search