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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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.