Ignore:
Timestamp:
05/01/13 08:56:48 (10 years ago)
Author:
fielding@…
Message:

Clarify that 405 is only for rejecting methods not supported by the target resource; addresses #146

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r2083 r2086  
    449449  }
    450450  @bottom-center {
    451        content: "Expires July 8, 2013";
     451       content: "Expires July 9, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-01-04">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-01-05">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">January 4, 2013</td>
     522               <td class="right">January 5, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: July 8, 2013</td>
     525               <td class="left">Expires: July 9, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
    … …  
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on July 8, 2013.</p>
     553      <p>This Internet-Draft will expire on July 9, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    11651165      </p>
    11661166      <p id="rfc.section.3.1.1.p.9">HTTP does not place a pre-defined limit on the length of a request-line. A server that receives a method longer than any that
    1167          it implements <em class="bcp14">SHOULD</em> respond with either a <a href="p2-semantics.html#status.405" class="smpl">405 (Method Not Allowed)</a>, if it is an origin server, or a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code if the received request-target would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
     1167         it implements <em class="bcp14">SHOULD</em> respond with a <a href="p2-semantics.html#status.501" class="smpl">501 (Not Implemented)</a> status code. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the <a href="p2-semantics.html#status.414" class="smpl">414 (URI Too Long)</a> status code if the received request-target would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
    11681168      </p>
    11691169      <p id="rfc.section.3.1.1.p.10">Various ad-hoc limitations on request-line length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support, at a minimum, request-line lengths of 8000 octets.

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2083 r2086  
    11011101   HTTP does not place a pre-defined limit on the length of a request-line.
    11021102   A server that receives a method longer than any that it implements
    1103    &SHOULD; respond with either a <x:ref>405 (Method Not Allowed)</x:ref>, if it is an origin
    1104    server, or a <x:ref>501 (Not Implemented)</x:ref> status code.
     1103   &SHOULD; respond with a <x:ref>501 (Not Implemented)</x:ref> status code.
    11051104   A server &MUST; be prepared to receive URIs of unbounded length and
    11061105   respond with the <x:ref>414 (URI Too Long)</x:ref> status code if the received
    … …  
    39233922    <x:defines>4xx</x:defines>
    39243923    <x:defines>400 (Bad Request)</x:defines>
    3925     <x:defines>405 (Method Not Allowed)</x:defines>
    39263924    <x:defines>411 (Length Required)</x:defines>
    39273925    <x:defines>414 (URI Too Long)</x:defines>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r2085 r2086  
    13291329         to be registered within the HTTP Method Registry maintained by IANA, as defined in <a href="#method.registry" title="Method Registry">Section&nbsp;8.1</a>.
    13301330      </p>
    1331       <p id="rfc.section.4.1.p.8">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.4.1</a>). However, the set of allowed methods can change dynamically. When a request message is received that is unrecognized or
    1332          not implemented by an origin server, the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.501" class="smpl">501 (Not Implemented)</a> status code. When a request message is received that is known by an origin server but not allowed for the target resource,
     1331      <p id="rfc.section.4.1.p.8">The set of methods allowed by a target resource can be listed in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;7.4.1</a>). However, the set of allowed methods can change dynamically. When a request method is received that is unrecognized or not
     1332         implemented by an origin server, the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.501" class="smpl">501 (Not Implemented)</a> status code. When a request method is received that is known by an origin server but not allowed for the target resource,
    13331333         the origin server <em class="bcp14">SHOULD</em> respond with the <a href="#status.405" class="smpl">405 (Method Not Allowed)</a> status code.
    13341334      </p>
    … …  
    26382638      <div id="rfc.iref.74"></div>
    26392639      <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    2640       <p id="rfc.section.6.5.5.p.1">The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method specified in the request-line is not allowed by the origin server for the <a href="#resources" class="smpl">target resource</a>. The origin server <em class="bcp14">MUST</em> generate an <a href="#header.allow" class="smpl">Allow</a> header field in the response containing a list of valid methods for the requested resource.
     2640      <p id="rfc.section.6.5.5.p.1">The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method specified in the request-line is known by the origin server but not supported by the <a href="#resources" class="smpl">target resource</a>. The origin server <em class="bcp14">MUST</em> generate an <a href="#header.allow" class="smpl">Allow</a> header field in a 405 response containing a list of the target resource's currently supported methods.
    26412641      </p>
    26422642      <div id="rfc.iref.74"></div>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2085 r2086  
    11161116   <x:ref>Allow</x:ref> header field (<xref target="header.allow"/>).
    11171117   However, the set of allowed methods can change dynamically.
    1118    When a request message is received that is unrecognized or not implemented
     1118   When a request method is received that is unrecognized or not implemented
    11191119   by an origin server, the origin server &SHOULD; respond with the
    11201120   <x:ref>501 (Not Implemented)</x:ref> status code.
    1121    When a request message is received that is known by an origin server but
     1121   When a request method is received that is known by an origin server but
    11221122   not allowed for the target resource, the origin server &SHOULD; respond
    11231123   with the <x:ref>405 (Method Not Allowed)</x:ref> status code.
    … …  
    32003200<t>
    32013201   The <x:dfn>405 (Method Not Allowed)</x:dfn> status code indicates that the
    3202    method specified in the request-line is not allowed by the origin server
    3203    for the <x:ref>target resource</x:ref>. The origin server &MUST; generate
    3204    an <x:ref>Allow</x:ref> header field in the response containing a list of
    3205    valid methods for the requested resource.
     3202   method specified in the request-line is known by the origin server but
     3203   not supported by the <x:ref>target resource</x:ref>.
     3204   The origin server &MUST; generate an <x:ref>Allow</x:ref> header field in
     3205   a 405 response containing a list of the target resource's currently
     3206   supported methods.
    32063207</t>
    32073208</section>
Note: See TracChangeset for help on using the changeset viewer.