- From: Paul Hoffman <paul.hoffman@gmail.com>
- Date: Thu, 7 May 2015 13:34:58 -0700
- To: Julian Reschke <julian.reschke@greenbytes.de>
- Cc: RFC Errata System <rfc-editor@rfc-editor.org>, fielding@gbiv.com, ylafon@w3.org, barryleiba@computer.org, Mark Nottingham <mnot@mnot.net>, elatllat@gmail.com, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
- Message-ID: <CAPik8ya0Xd5RAEcMbvt4VV0UDB4UPM1c=hAxZLSW=gmnrCjO_Q@mail.gmail.com>
It sounds like a technical addition, not a technical change. Regardless, it doesn't seem like an actual errata unless this topic came up during WG discussion, was agreed to, but then it somehow didn't make it into the RFC. Further, given that this is a "MAY", the second paragraph of the "Notes" seems overblown, given that some browsers have figured out a way to do this without breaking the spec. On Thu, May 7, 2015 at 12:39 PM, Julian Reschke < julian.reschke@greenbytes.de> wrote: > Unless I'm missing something this sounds like a technical change to me. > > Best regards, Julian > > > On 2015-05-07 20:43, RFC Errata System wrote: > >> 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=4358 >> >> -------------------------------------- >> Type: Technical >> Reported by: Tim <elatllat@gmail.com> >> >> Section: 4 >> >> Original Text >> ------------- >> 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). >> >> Corrected Text >> -------------- >> 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. >> >> 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 >> Area : Applications >> Stream : IETF >> Verifying Party : IESG >> >> > > -- > <green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany > Amtsgericht Münster: HRB5782 > >
Received on Thursday, 7 May 2015 20:35:28 UTC