Ignore:
Timestamp:
15/09/13 00:57:24 (7 years ago)
Author:
fielding@…
Message:

uniform terminology for status code and request method (except where it is obvious by context)

File:
1 edited

Legend:

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

    r2398 r2400  
    19681968   The "Max-Forwards" header field provides a mechanism with the
    19691969   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
    1970    methods to limit the number of times that the request is forwarded by
     1970   request methods to limit the number of times that the request is forwarded by
    19711971   proxies. This can be useful when the client is attempting to
    19721972   trace a request that appears to be failing or looping mid-chain.
     
    27292729</t>
    27302730<t>
    2731    A client &MUST; be able to parse one or more 1xx status responses received
     2731   A client &MUST; be able to parse one or more 1xx responses received
    27322732   prior to a final response, even if the client does not expect one.
    2733    A user agent &MAY; ignore unexpected 1xx status responses.
     2733   A user agent &MAY; ignore unexpected 1xx responses.
    27342734</t>
    27352735<t>
     
    33223322   server did not find a current representation for the
    33233323   <x:ref>target resource</x:ref> or is not willing to disclose that one
    3324    exists. A 404 status does not indicate whether this lack of representation
     3324   exists. A 404 status code does not indicate whether this lack of representation
    33253325   is temporary or permanent; the <x:ref>410 (Gone)</x:ref> status code is
    33263326   preferred over 404 if the origin server knows, presumably through some
     
    33383338<t>
    33393339   The <x:dfn>405 (Method Not Allowed)</x:dfn> status code indicates that the
    3340    method specified in the request-line is known by the origin server but
     3340   method received in the request-line is known by the origin server but
    33413341   not supported by the <x:ref>target resource</x:ref>.
    33423342   The origin server &MUST; generate an <x:ref>Allow</x:ref> header field in
     
    34943494   The <x:dfn>415 (Unsupported Media Type)</x:dfn> status code indicates that
    34953495   the origin server is refusing to service the request because the payload is
    3496    in a format not supported by the <x:ref>target resource</x:ref> for this
    3497    method. The format problem might be due to the request's indicated
     3496   in a format not supported by this method on the <x:ref>target resource</x:ref>.
     3497   The format problem might be due to the request's indicated
    34983498   <x:ref>Content-Type</x:ref> or <x:ref>Content-Encoding</x:ref>, or as a
    34993499   result of inspecting the data directly.
Note: See TracChangeset for help on using the changeset viewer.