Ignore:
Timestamp:
Jul 24, 2010, 6:56:20 AM (9 years ago)
Author:
ylafon@…
Message:

uniform use of 'status' (see #234)

File:
1 edited

Legend:

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

    r921 r924  
    616616<t>
    617617  The HTTP Status Code Registry defines the name space for the Status-Code
    618   token in the Status line of an HTTP response.
     618  token in the Status-Line of an HTTP response.
    619619</t>
    620620<t>
     
    695695   <t>If the response status code is 200 or 203 and the request method was GET,
    696696   the response is a representation of the resource at the Effective Request URI.</t>
    697    <t>If the response status is 204, 206, or 304 and the request method was GET
     697   <t>If the response status code is 204, 206, or 304 and the request method was GET
    698698   or HEAD, the response is a partial representation of the resource at the
    699699   Effective Request URI (see &caching-combining-headers;).</t>
     
    929929   The action performed by the POST method might not result in a
    930930   resource that can be identified by a URI. In this case, either 200
    931    (OK) or 204 (No Content) is the appropriate response status,
     931   (OK) or 204 (No Content) is the appropriate response status code,
    932932   depending on whether or not the response includes a representation that
    933933   describes the result.
     
    985985   responses for the Effective Request URI, those stored responses
    986986   &SHOULD; be marked as stale if the response to the PUT request
    987    is a success status. Responses to the PUT method are not cacheable.
     987   has a success status code. Responses to the PUT method are
     988   not cacheable.
    988989</t>
    989990<t>
     
    12671268   header fields refer to the requested resource and its current
    12681269   representation, respectively, after the requested action.
    1269    For example, if a 204 status is received in response to a PUT
     1270   For example, if a 204 status code is received in response to a PUT
    12701271   and the response contains an ETag header field, then the value of
    12711272   that field is the current entity-tag for the representation that
     
    14591460</t>
    14601461<t>
    1461    The 303 status is generally applicable to any HTTP method.  It is
     1462   The 303 status code is generally applicable to any HTTP method.  It is
    14621463   primarily used to allow the output of a POST action to redirect
    14631464   the user agent to a selected resource, since doing so provides the
     
    15011502  <iref primary="true" item="Status Codes" subitem="305 Use Proxy" x:for-anchor=""/>
    15021503<t>
    1503    The 305 status was defined in a previous version of this specification
     1504   The 305 status code was defined in a previous version of this specification
    15041505   (see <xref target="changes.from.rfc.2616"/>), and is now deprecated.
    15051506</t>
     
    15281529   response &SHOULD; contain a short hypertext note with a hyperlink to
    15291530   the new URI(s) , since many pre-HTTP/1.1 user agents do not
    1530    understand the 307 status. Therefore, the note &SHOULD; contain the
     1531   understand the 307 status code. Therefore, the note &SHOULD; contain the
    15311532   information necessary for a user to repeat the original request on
    15321533   the new URI.
     
    19921993   A server that does not understand or is unable to comply with any of
    19931994   the expectation values in the Expect field of a request &MUST; respond
    1994    with appropriate error status. The server &MUST; respond with a 417
    1995    (Expectation Failed) status if any of the expectations cannot be met
     1995   with appropriate error status code. The server &MUST; respond with a 417
     1996   (Expectation Failed) status code if any of the expectations cannot be met
    19961997   or, if there are other problems with the request, some other 4xx
    1997    status.
     1998   status code.
    19981999</t>
    19992000<t>
     
    20012002   future extensions. If a server receives a request containing an
    20022003   Expect field that includes an expectation-extension that it does not
    2003    support, it &MUST; respond with a 417 (Expectation Failed) status.
     2004   support, it &MUST; respond with a 417 (Expectation Failed) status code.
    20042005</t>
    20052006<t>
     
    20102011<t>
    20112012   The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy &MUST;
    2012    return a 417 (Expectation Failed) status if it receives a request
     2013   return a 417 (Expectation Failed) status code if it receives a request
    20132014   with an expectation that it cannot meet. However, the Expect
    20142015   request-header itself is end-to-end; it &MUST; be forwarded if the
     
    20202021</t>
    20212022<t>
    2022    See &use100; for the use of the 100 (Continue) status.
     2023   See &use100; for the use of the 100 (Continue) status code.
    20232024</t>
    20242025</section>
Note: See TracChangeset for help on using the changeset viewer.