Ignore:
Timestamp:
Jul 4, 2012, 10:59:15 AM (7 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

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

    r1712 r1713  
    391391   always notifies the client whether a method is currently allowed on a
    392392   resource, since the set of allowed methods can change dynamically. An
    393    origin server &SHOULD; respond with the status code 405 (Method Not Allowed)
     393   origin server &SHOULD; respond with the status code <x:ref>405 (Method Not Allowed)</x:ref>
    394394   if the method is known by the origin server but not allowed for the
    395395   resource, and <x:ref>501 (Not Implemented)</x:ref> if the method is
     
    731731   representation or changing the resource configuration, or respond
    732732   with an appropriate error message containing sufficient information
    733    to explain why the representation is unsuitable.  The 409 (Conflict)
    734    or 415 (Unsupported Media Type) status codes are suggested, with the
     733   to explain why the representation is unsuitable.  The <x:ref>409 (Conflict)</x:ref>
     734   or <x:ref>415 (Unsupported Media Type)</x:ref> status codes are suggested, with the
    735735   latter being specific to constraints on Content-Type values.
    736736</t>
     
    17641764  <iref primary="true" item="400 Bad Request (status code)" x:for-anchor=""/>
    17651765  <iref primary="true" item="Status Codes" subitem="400 Bad Request" x:for-anchor=""/>
     1766  <x:anchor-alias value="400 (Bad Request)"/>
    17661767<t>
    17671768   The server cannot or will not process the request, due to a client error (e.g.,
     
    17811782  <iref primary="true" item="403 Forbidden (status code)" x:for-anchor=""/>
    17821783  <iref primary="true" item="Status Codes" subitem="403 Forbidden" x:for-anchor=""/>
     1784  <x:anchor-alias value="403 (Forbidden)"/>
    17831785<t>
    17841786   The server understood the request, but refuses to authorize it. Providing
     
    17911793   public why the request has not been fulfilled, it &SHOULD; describe the
    17921794   reason for the refusal in the representation.  If the server does not wish to
    1793    make this information available to the client, the status code 404
    1794    (Not Found) &MAY; be used instead.
     1795   make this information available to the client, the status code <x:ref>404
     1796   (Not Found)</x:ref> &MAY; be used instead.
    17951797</t>
    17961798</section>
     
    17991801  <iref primary="true" item="404 Not Found (status code)" x:for-anchor=""/>
    18001802  <iref primary="true" item="Status Codes" subitem="404 Not Found" x:for-anchor=""/>
     1803  <x:anchor-alias value="404 (Not Found)"/>
    18011804<t>
    18021805   The server has not found anything matching the effective request URI. No
    18031806   indication is given of whether the condition is temporary or
    1804    permanent. The 410 (Gone) status code &SHOULD; be used if the server
     1807   permanent. The <x:ref>410 (Gone)</x:ref> status code &SHOULD; be used if the server
    18051808   knows, through some internally configurable mechanism, that an old
    18061809   resource is permanently unavailable and has no forwarding address.
     
    18141817  <iref primary="true" item="405 Method Not Allowed (status code)" x:for-anchor=""/>
    18151818  <iref primary="true" item="Status Codes" subitem="405 Method Not Allowed" x:for-anchor=""/>
     1819  <x:anchor-alias value="405 (Method Not Allowed)"/>
    18161820<t>
    18171821   The method specified in the request-line is not allowed for the target
     
    18241828  <iref primary="true" item="406 Not Acceptable (status code)" x:for-anchor=""/>
    18251829  <iref primary="true" item="Status Codes" subitem="406 Not Acceptable" x:for-anchor=""/>
     1830  <x:anchor-alias value="406 (Not Acceptable)"/>
    18261831<t>
    18271832   The resource identified by the request is only capable of generating
     
    18671872  <iref primary="true" item="409 Conflict (status code)" x:for-anchor=""/>
    18681873  <iref primary="true" item="Status Codes" subitem="409 Conflict" x:for-anchor=""/>
     1874  <x:anchor-alias value="409 (Conflict)"/>
    18691875<t>
    18701876   The request could not be completed due to a conflict with the current
     
    18911897  <iref primary="true" item="410 Gone (status code)" x:for-anchor=""/>
    18921898  <iref primary="true" item="Status Codes" subitem="410 Gone" x:for-anchor=""/>
     1899  <x:anchor-alias value="410 (Gone)"/>
    18931900<t>
    18941901   The target resource is no longer available at the server and no
     
    18971904   delete references to the effective request URI after user approval. If the
    18981905   server does not know, or has no facility to determine, whether or not
    1899    the condition is permanent, the status code 404 (Not Found) &SHOULD; be
    1900    used instead.
     1906   the condition is permanent, the status code <x:ref>404 (Not Found)</x:ref>
     1907   &SHOULD; be used instead.
    19011908</t>
    19021909<t>
     
    19201927  <iref primary="true" item="411 Length Required (status code)" x:for-anchor=""/>
    19211928  <iref primary="true" item="Status Codes" subitem="411 Length Required" x:for-anchor=""/>
     1929  <x:anchor-alias value="411 (Length Required)"/>
    19221930<t>
    19231931   The server refuses to accept the request without a defined Content-Length.
     
    19471955  <iref primary="true" item="414 URI Too Long (status code)" x:for-anchor=""/>
    19481956  <iref primary="true" item="Status Codes" subitem="414 URI Too Long" x:for-anchor=""/>
     1957  <x:anchor-alias value="414 (URI Too Long)"/>
    19491958<t>
    19501959   The server is refusing to service the request because the effective request URI
     
    19631972  <iref primary="true" item="415 Unsupported Media Type (status code)" x:for-anchor=""/>
    19641973  <iref primary="true" item="Status Codes" subitem="415 Unsupported Media Type" x:for-anchor=""/>
     1974  <x:anchor-alias value="415 (Unsupported Media Type)"/>
    19651975<t>
    19661976   The server is refusing to service the request because the request
     
    19731983  <iref primary="true" item="417 Expectation Failed (status code)" x:for-anchor=""/>
    19741984  <iref primary="true" item="Status Codes" subitem="417 Expectation Failed" x:for-anchor=""/>
     1985  <x:anchor-alias value="417 (Expectation Failed)"/>
    19751986<t>
    19761987   The expectation given in an Expect header field (see <xref target="header.expect"/>)
     
    19841995  <iref primary="true" item="426 Upgrade Required (status code)" x:for-anchor=""/>
    19851996  <iref primary="true" item="Status Codes" subitem="426 Upgrade Required" x:for-anchor=""/>
     1997  <x:anchor-alias value="426 (Upgrade Required)"/>
    19861998<t>
    19871999   The request can not be completed without a prior protocol upgrade. This
     
    28532865   but it cannot expect responses to always honor them. For example, the origin
    28542866   server might not implement server-driven negotiation, or it might decide that
    2855    sending a response that doesn't conform to them is better than sending a 406
    2856    (Not Acceptable) response.
     2867   sending a response that doesn't conform to them is better than sending a <x:ref>406
     2868   (Not Acceptable)</x:ref> response.
    28572869</t>
    28582870<t>
     
    29132925</t>
    29142926<t>
    2915    This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable)
     2927   This specification defines the 300 (Multiple Choices) and <x:ref>406 (Not Acceptable)</x:ref>
    29162928   status codes for enabling agent-driven negotiation when the server is
    29172929   unwilling or unable to provide a varying response using server-driven
     
    29933005   If an Accept header field is present in a request and none of the
    29943006   available representations for the response have a media type that is
    2995    listed as acceptable, the origin server &MAY; either
    2996    honor the Accept header field by sending a 406 (Not Acceptable) response
     3007   listed as acceptable, the origin server &MAY; either honor the Accept
     3008   header field by sending a <x:ref>406 (Not Acceptable)</x:ref> response
    29973009   or disregard the Accept header field by treating the response as if
    29983010   it is not subject to content negotiation.
     
    30943106   available representations for the response have a character encoding that
    30953107   is listed as acceptable, the origin server &MAY; either honor the
    3096    Accept-Charset header field by sending a 406 (Not Acceptable) response or
     3108   Accept-Charset header field by sending a <x:ref>406 (Not Acceptable)</x:ref> response or
    30973109   disregard the Accept-Charset header field by treating the response as if
    30983110   it is not subject to content negotiation.
     
    35783590   If all received Expect header field(s) are syntactically valid but contain
    35793591   an expectation that the recipient does not understand or cannot comply with,
    3580    the recipient &MUST; respond with a 417 (Expectation Failed) status code. A
     3592   the recipient &MUST; respond with a <x:ref>417 (Expectation Failed)</x:ref> status code. A
    35813593   recipient of a syntactically invalid Expectation header field &MUST; respond
    35823594   with a 4xx status code other than 417.
Note: See TracChangeset for help on using the changeset viewer.