Ignore:
Timestamp:
14/01/13 01:45:45 (8 years ago)
Author:
fielding@…
Message:

(editorial) shorten reason phrase for 416 to Range Not Satisfiable

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r2080 r2121  
    286286</section>
    287287
    288 <section title="416 Requested Range Not Satisfiable" anchor="status.416">
    289   <iref primary="true" item="416 Requested Range Not Satisfiable (status code)" x:for-anchor=""/>
    290   <x:anchor-alias value="416 (Requested Range Not Satisfiable)"/>
    291 <t>
    292    The <x:dfn>416 (Requested Range Not Satisfiable)</x:dfn> status code
     288<section title="416 Range Not Satisfiable" anchor="status.416">
     289  <iref primary="true" item="416 Range Not Satisfiable (status code)" x:for-anchor=""/>
     290  <x:anchor-alias value="416 (Range Not Satisfiable)"/>
     291<t>
     292   The <x:dfn>416 (Range Not Satisfiable)</x:dfn> status code
    293293   indicates that none of the ranges-specifier values in the request's
    294294   <x:ref>Range</x:ref> header field (<xref target="header.range"/>)
     
    309309<preamble>For example:</preamble>
    310310<artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
    311 HTTP/1.1 416 Requested Range Not Satisfiable
     311HTTP/1.1 416 Range Not Satisfiable
    312312Date: Mon, 20 Jan 2012 15:41:54 GMT
    313313Content-Range: bytes */47022
     
    520520</t>
    521521<t>
    522    In the case of a byte range request:
    523    a server sending a response with status code <x:ref>416 (Requested Range Not
    524    Satisfiable)</x:ref> &SHOULD; send a Content-Range field with a byte-range-resp-spec
    525    of "*". The instance-length specifies the current length of
    526    the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref>
    527    &MUST-NOT; send a Content-Range field with a byte-range-resp-spec of "*".
     522   In the case of a byte range request: a server sending a response with
     523   status code <x:ref>416 (Range Not Satisfiable)</x:ref> &SHOULD; send a
     524   Content-Range field with a byte-range-resp-spec of "*".
     525   The instance-length specifies the current length of the selected resource.
     526   A server &MUST-NOT; generate a a Content-Range field with a
     527   byte-range-resp-spec of "*" in a <x:ref>206 (Partial Content)</x:ref>
     528   response.
    528529</t>
    529530<t>
    530531  The "Content-Range" header field has no meaning for status codes that do not
    531532  explicitly describe its semantic. Currently, only status codes
    532   <x:ref>206 (Partial Content)</x:ref> and <x:ref>416 (Requested Range Not Satisfiable)</x:ref> describe
     533  <x:ref>206 (Partial Content)</x:ref> and <x:ref>416 (Range Not Satisfiable)</x:ref> describe
    533534  the meaning of this header field.
    534535</t>
     
    700701   Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
    701702   is unsatisfiable, the server &SHOULD; send a response with a
    702    <x:ref>416 (Requested Range Not Satisfiable)</x:ref> status code. Otherwise, the server
     703   <x:ref>416 (Range Not Satisfiable)</x:ref> status code. Otherwise, the server
    703704   &SHOULD; send a response with a <x:ref>206 (Partial Content)</x:ref> status code
    704705   containing the satisfiable ranges of the representation.
     
    823824   </c>
    824825   <c>416</c>
    825    <c>Requested Range Not Satisfiable</c>
     826   <c>Range Not Satisfiable</c>
    826827   <c>
    827828      <xref target="status.416"/>
Note: See TracChangeset for help on using the changeset viewer.