Changeset 2121


Ignore:
Timestamp:
Jan 13, 2013, 5:45:45 PM (7 years ago)
Author:
fielding@…
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2120 r2121  
    23422342               <tr>
    23432343                  <td class="left">416</td>
    2344                   <td class="left">Requested Range Not Satisfiable</td>
    2345                   <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
     2344                  <td class="left">Range Not Satisfiable</td>
     2345                  <td id="status.416" class="left"><a href="p5-range.html#status.416" title="416 Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></td>
    23462346               </tr>
    23472347               <tr>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2120 r2121  
    26462646  <c>414</c> <c>URI Too Long</c> <c><xref target="status.414"/></c>
    26472647  <c>415</c> <c>Unsupported Media Type</c> <c><xref target="status.415"/></c>
    2648   <c>416</c> <c>Requested Range Not Satisfiable</c> <c anchor="status.416">&status-416;</c>
     2648  <c>416</c> <c>Range Not Satisfiable</c> <c anchor="status.416">&status-416;</c>
    26492649  <c>417</c> <c>Expectation Failed</c> <c><xref target="status.417"/></c>
    26502650  <c>426</c> <c>Upgrade Required</c> <c><xref target="status.426"/></c>
  • draft-ietf-httpbis/latest/p5-range.html

    r2116 r2121  
    449449  }
    450450  @bottom-center {
    451        content: "Expires July 16, 2013";
     451       content: "Expires July 17, 2013";
    452452  }
    453453  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2013-01-12">
     495      <meta name="dct.issued" scheme="ISO8601" content="2013-01-13">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: July 16, 2013</td>
     521               <td class="left">Expires: July 17, 2013</td>
    522522               <td class="right">J. Reschke, Editor</td>
    523523            </tr>
     
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">January 12, 2013</td>
     530               <td class="right">January 13, 2013</td>
    531531            </tr>
    532532         </tbody>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on July 16, 2013.</p>
     555      <p>This Internet-Draft will expire on July 17, 2013.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    582582         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
    583583               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    584                <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     584               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Range Not Satisfiable</a></li>
    585585            </ul>
    586586         </li>
     
    698698      </p>
    699699      <div id="rfc.iref.3"></div>
    700       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>
    701       <p id="rfc.section.3.2.p.1">The <dfn>416 (Requested Range Not Satisfiable)</dfn> status code indicates that none of the ranges-specifier values in the request's <a href="#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>) overlap the current extent of the selected resource and the request did not include an <a href="#header.if-range" class="smpl">If-Range</a> header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
     700      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Range Not Satisfiable</a></h2>
     701      <p id="rfc.section.3.2.p.1">The <dfn>416 (Range Not Satisfiable)</dfn> status code indicates that none of the ranges-specifier values in the request's <a href="#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>) overlap the current extent of the selected resource and the request did not include an <a href="#header.if-range" class="smpl">If-Range</a> header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
    702702         length of the selected representation.)
    703703      </p>
     
    705705      </p>
    706706      <div id="rfc.figure.u.2"></div>
    707       <p>For example:</p>  <pre class="text">HTTP/1.1 416 Requested Range Not Satisfiable
     707      <p>For example:</p>  <pre class="text">HTTP/1.1 416 Range Not Satisfiable
    708708Date: Mon, 20 Jan 2012 15:41:54 GMT
    709709Content-Range: bytes */47022
    710710Content-Type: image/gif
    711711</pre><div class="note" id="rfc.section.3.2.p.4">
    712          <p> <b>Note:</b> Clients cannot depend on servers to send a <a href="#status.416" class="smpl">416 (Requested
    713                Range Not Satisfiable)</a> response instead of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response for an unsatisfiable <a href="#range.retrieval.requests" class="smpl">Range</a> header field, since not all servers implement this header field.
     712         <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested
     713            Range Not Satisfiable) response instead of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response for an unsatisfiable <a href="#range.retrieval.requests" class="smpl">Range</a> header field, since not all servers implement this header field.
    714714         </p>
    715715      </div>
     
    802802         whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
    803803      </p>
    804       <p id="rfc.section.5.2.p.7">In the case of a byte range request: a server sending a response with status code <a href="#status.416" class="smpl">416 (Requested Range Not
    805             Satisfiable)</a>  <em class="bcp14">SHOULD</em> send a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the selected
    806          resource. A response with status code <a href="#status.206" class="smpl">206 (Partial Content)</a>  <em class="bcp14">MUST NOT</em> send a Content-Range field with a byte-range-resp-spec of "*".
     804      <p id="rfc.section.5.2.p.7">In the case of a byte range request: a server sending a response with status code <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a>  <em class="bcp14">SHOULD</em> send a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the selected
     805         resource. A server <em class="bcp14">MUST NOT</em> generate a a Content-Range field with a byte-range-resp-spec of "*" in a <a href="#status.206" class="smpl">206 (Partial Content)</a> response.
    807806      </p>
    808807      <p id="rfc.section.5.2.p.8">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. Currently,
    809          only status codes <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Requested Range Not Satisfiable)</a> describe the meaning of this header field.
     808         only status codes <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> describe the meaning of this header field.
    810809      </p>
    811810      <p id="rfc.section.5.2.p.9">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
     
    885884      <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
    886885         length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
    887          is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> send a response with a <a href="#status.416" class="smpl">416 (Requested Range Not Satisfiable)</a> status code. Otherwise, the server <em class="bcp14">SHOULD</em> send a response with a <a href="#status.206" class="smpl">206 (Partial Content)</a> status code containing the satisfiable ranges of the representation.
     886         is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> send a response with a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status code. Otherwise, the server <em class="bcp14">SHOULD</em> send a response with a <a href="#status.206" class="smpl">206 (Partial Content)</a> status code containing the satisfiable ranges of the representation.
    888887      </p>
    889888      <p id="rfc.section.5.4.1.p.12">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of an HTTP payload, recipients <em class="bcp14">SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
     
    956955               <tr>
    957956                  <td class="left">416</td>
    958                   <td class="left">Requested Range Not Satisfiable</td>
    959                   <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
     957                  <td class="left">Range Not Satisfiable</td>
     958                  <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;3.2</a>
    960959                  </td>
    961960               </tr>
     
    13301329            </li>
    13311330            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    1332                   <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">6.1</a></li>
     1331                  <li>416 Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">6.1</a></li>
    13331332               </ul>
    13341333            </li>
  • 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.