Ignore:
Timestamp:
Jul 4, 2012, 12:54:55 PM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (2xx range)

File:
1 edited

Legend:

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

    r1714 r1715  
    665665</t>
    666666<t>
    667    The action performed by the POST method might not result in a
    668    resource that can be identified by a URI. In this case, either 200
    669    (OK) or 204 (No Content) is the appropriate response status code,
    670    depending on whether or not the response includes a representation that
    671    describes the result.
     667   The action performed by the POST method might not result in a resource that
     668   can be identified by a URI. In this case, either <x:ref>200 (OK)</x:ref> or
     669   <x:ref>204 (No Content)</x:ref> is the appropriate response status
     670   code, depending on whether or not the response includes a representation
     671   that describes the result.
    672672</t>
    673673<t>
    674674   If a resource has been created on the origin server, the response
    675    &SHOULD; be 201 (Created) and contain a representation which describes the
    676    status of the request and refers to the new resource, and a Location
    677    header field (see <xref target="header.location"/>).
     675   &SHOULD; be <x:ref>201 (Created)</x:ref> and contain a representation which
     676   describes the status of the request and refers to the new resource, and a
     677   Location header field (see <xref target="header.location"/>).
    678678</t>
    679679<t>
     
    700700   representation would suggest that a subsequent GET on that same target
    701701   resource will result in an equivalent representation being returned in
    702    a 200 (OK) response.  However, there is no guarantee that such a state
    703    change will be observable, since the target resource might be acted
    704    upon by other user agents in parallel, or might be subject to dynamic
     702   a <x:ref>200 (OK)</x:ref> response.  However, there is no guarantee that
     703   such a state change will be observable, since the target resource might be
     704   acted upon by other user agents in parallel, or might be subject to dynamic
    705705   processing by the origin server, before any subsequent GET is received.
    706706   A successful response only implies that the user agent's intent was
     
    710710   If the target resource does not have a current representation and
    711711   the PUT successfully creates one, then the origin server &MUST; inform
    712    the user agent by sending a 201 (Created) response.  If the target
    713    resource does have a current representation and that representation is
     712   the user agent by sending a <x:ref>201 (Created)</x:ref> response.  If the
     713   target resource does have a current representation and that representation is
    714714   successfully modified in accordance with the state of the enclosed
    715    representation, then either a 200 (OK) or 204 (No Content) response
    716    &SHOULD; be sent to indicate successful completion of the request.
     715   representation, then either a <x:ref>200 (OK)</x:ref> or <x:ref>204 (No Content)</x:ref>
     716   response &SHOULD; be sent to indicate successful completion of the request.
    717717</t>
    718718<t>
     
    828828</t>
    829829<t>
    830    A successful response &SHOULD; be 200 (OK) if the response includes an
    831    representation describing the status, 202 (Accepted) if the action has not
    832    yet been enacted, or 204 (No Content) if the action has been enacted
    833    but the response does not include a representation.
     830   A successful response &SHOULD; be <x:ref>200 (OK)</x:ref> if the response
     831   includes an representation describing the status, <x:ref>202 (Accepted)</x:ref>
     832   if the action has not yet been enacted, or <x:ref>204 (No Content)</x:ref> if
     833   the action has been enacted but the response does not include a representation.
    834834</t>
    835835<t>
     
    855855   The TRACE method requests a remote, application-layer loop-back
    856856   of the request message. The final recipient of the request
    857    &SHOULD; reflect the message received back to the client as the
    858    message body of a 200 (OK) response. The final recipient is either the
     857   &SHOULD; reflect the message received back to the client as the message body
     858   of a <x:ref>200 (OK)</x:ref> response. The final recipient is either the
    859859   origin server or the first proxy to receive a Max-Forwards
    860860   value of zero (0) in the request (see <xref target="header.max-forwards"/>).
     
    13491349  <iref primary="true" item="200 OK (status code)" x:for-anchor=""/>
    13501350  <iref primary="true" item="Status Codes" subitem="200 OK" x:for-anchor=""/>
     1351  <x:anchor-alias value="200 (OK)"/>
    13511352<t>
    13521353   The request has succeeded. The payload returned with the response
     
    13771378  <iref primary="true" item="201 Created (status code)" x:for-anchor=""/>
    13781379  <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/>
     1380  <x:anchor-alias value="201 (Created)"/>
    13791381<t>
    13801382   The request has been fulfilled and has resulted in one or more new resources
     
    13911393   The origin server &MUST; create the resource(s) before returning the 201 status
    13921394   code. If the action cannot be carried out immediately, the server &SHOULD;
    1393    respond with 202 (Accepted) response instead.
     1395   respond with <x:ref>202 (Accepted)</x:ref> response instead.
    13941396</t>
    13951397<t>
     
    14041406  <iref primary="true" item="202 Accepted (status code)" x:for-anchor=""/>
    14051407  <iref primary="true" item="Status Codes" subitem="202 Accepted" x:for-anchor=""/>
     1408  <x:anchor-alias value="202 (Accepted)"/>
    14061409<t>
    14071410   The request has been accepted for processing, but the processing has
     
    14261429  <iref primary="true" item="203 Non-Authoritative Information (status code)" x:for-anchor=""/>
    14271430  <iref primary="true" item="Status Codes" subitem="203 Non-Authoritative Information" x:for-anchor=""/>
     1431  <x:anchor-alias value="203 (Non-Authoritative Information)"/>
    14281432<t>
    14291433   The representation in the response has been transformed or otherwise
     
    14341438<t>
    14351439   This status code is only appropriate when the response status code would
    1436    have been 200 (OK) otherwise. When the status code before transformation
    1437    would have been different, the 214 Transformation Applied warn-code
    1438    (&header-warning;) is appropriate.
     1440   have been <x:ref>200 (OK)</x:ref> otherwise. When the status code before
     1441   transformation would have been different, the 214 Transformation Applied
     1442   warn-code (&header-warning;) is appropriate.
    14391443</t>
    14401444<t>
     
    14471451  <iref primary="true" item="204 No Content (status code)" x:for-anchor=""/>
    14481452  <iref primary="true" item="Status Codes" subitem="204 No Content" x:for-anchor=""/>
     1453  <x:anchor-alias value="204 (No Content)"/>
    14491454<t>
    14501455   The 204 (No Content) status code indicates that the server has
     
    17171722  <iref primary="true" item="305 Use Proxy (status code)" x:for-anchor=""/>
    17181723  <iref primary="true" item="Status Codes" subitem="305 Use Proxy" x:for-anchor=""/>
     1724  <x:anchor-alias value="305 (Use Proxy)"/>
    17191725<t>
    17201726   The 305 status code was defined in a previous version of this specification
     
    26232629   by the effective request URI).  The precise semantics of a representation
    26242630   are determined by the type of message (request or response), the request
    2625    method, the response status code, and the representation metadata.
    2626    For example, the above semantic is true for the representation in any
    2627    200 (OK) response to GET and for the representation in any PUT request.
     2631   method, the response status code, and the representation metadata. For
     2632   example, the above semantic is true for the representation in any
     2633   <x:ref>200 (OK)</x:ref> response to GET and for the representation in any PUT request.
    26282634   A 200 response to PUT, in contrast, contains either a representation
    26292635   that describes the successful action or a representation of the target
     
    36883694</artwork></figure>
    36893695<t>
    3690    For 201 (Created) responses, the Location is the URI of the new resource
    3691    which was created by the request. For 3xx responses, the location &SHOULD;
    3692    indicate the server's preferred URI for automatic redirection to the
    3693    resource.
     3696   For <x:ref>201 (Created)</x:ref> responses, the Location is the URI of the
     3697   new resource which was created by the request. For 3xx responses, the
     3698   location &SHOULD; indicate the server's preferred URI for automatic
     3699   redirection to the resource.
    36943700</t>
    36953701<t>
     
    37253731<t>
    37263732   There are circumstances in which a fragment identifier in a Location URI
    3727    would not be appropriate. For instance, when it appears in a 201 Created
    3728    response, where the Location header field specifies the URI for the entire
    3729    created resource.
     3733   would not be appropriate. For instance, when it appears in a <x:ref>201
     3734   (Created)</x:ref> response, where the Location header field specifies the
     3735   URI for the entire created resource.
    37303736</t>
    37313737<x:note>
     
    54105416</t>
    54115417<t>
    5412   Broadened the definition of 203 (Non-Authoritative Information) to include
    5413   cases of payload transformations as well.
     5418  Broadened the definition of <x:ref>203 (Non-Authoritative Information)</x:ref>
     5419  to include cases of payload transformations as well.
    54145420  (<xref target="status.203"/>)
    54155421</t>
     
    54305436</t>
    54315437<t>
    5432   Deprecate 305 Use Proxy status code, because user agents did not implement it.
    5433   It used to indicate that the target resource needs to be accessed through the
    5434   proxy given by the Location field. The Location field gave the URI of the
    5435   proxy. The recipient was expected to repeat this single request via the proxy.
     5438  Deprecate <x:ref>305 (Use Proxy)</x:ref> status code, because user agents did
     5439  not implement it. It used to indicate that the target resource needs to be
     5440  accessed through the proxy given by the Location field. The Location field
     5441  gave the URI of the proxy. The recipient was expected to repeat this single
     5442  request via the proxy.
    54365443  (<xref target="status.305"/>)
    54375444</t>
    54385445<t>
    5439   Define status 426 (Upgrade Required) (this was incorporated from
    5440   <xref target="RFC2817"/>).
     5446  Define status <x:ref>426 (Upgrade Required)</x:ref> (this was incorporated
     5447  from <xref target="RFC2817"/>).
    54415448  (<xref target="status.426"/>)
    54425449</t>
Note: See TracChangeset for help on using the changeset viewer.