Ignore:
Timestamp:
Jul 4, 2012, 1:44:42 AM (7 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

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

    r1708 r1710  
    392392   origin server &SHOULD; respond with the status code 405 (Method Not Allowed)
    393393   if the method is known by the origin server but not allowed for the
    394    resource, and 501 (Not Implemented) if the method is
     394   resource, and <x:ref>501 (Not Implemented)</x:ref> if the method is
    395395   unrecognized or not implemented by the origin server. The methods GET
    396396   and HEAD &MUST; be supported by all general-purpose servers. All other
     
    20302030  <iref primary="true" item="501 Not Implemented (status code)" x:for-anchor=""/>
    20312031  <iref primary="true" item="Status Codes" subitem="501 Not Implemented" x:for-anchor=""/>
     2032  <x:anchor-alias value="501 (Not Implemented)"/>
    20322033<t>
    20332034   The server does not support the functionality required to fulfill the
     
    20412042  <iref primary="true" item="502 Bad Gateway (status code)" x:for-anchor=""/>
    20422043  <iref primary="true" item="Status Codes" subitem="502 Bad Gateway" x:for-anchor=""/>
     2044  <x:anchor-alias value="502 (Bad Gateway)"/>
    20432045<t>
    20442046   The server, while acting as a gateway or proxy, received an invalid
     
    20512053  <iref primary="true" item="503 Service Unavailable (status code)" x:for-anchor=""/>
    20522054  <iref primary="true" item="Status Codes" subitem="503 Service Unavailable" x:for-anchor=""/>
     2055  <x:anchor-alias value="503 (Service Unavailable)"/>
    20532056<t>
    20542057   The server is currently unable to handle the request due to a
     
    20742077  <iref primary="true" item="504 Gateway Timeout (status code)" x:for-anchor=""/>
    20752078  <iref primary="true" item="Status Codes" subitem="504 Gateway Timeout" x:for-anchor=""/>
     2079  <x:anchor-alias value="504 (Gateway Timeout)"/>
    20762080<t>
    20772081   The server, while acting as a gateway or proxy, did not receive a
     
    20912095  <iref primary="true" item="505 HTTP Version Not Supported (status code)" x:for-anchor=""/>
    20922096  <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported" x:for-anchor=""/>
     2097  <x:anchor-alias value="505 (HTTP Version Not Supported)"/>
    20932098<t>
    20942099   The server does not support, or refuses to support, the protocol
     
    35163521
    35173522      <t>If the response status code conveys a server error, e.g., 500
    3518          (Internal Server Error) or 503 (Service Unavailable), and it is
    3519          inconvenient or impossible to generate a valid Date.</t>
     3523         (Internal Server Error) or <x:ref>503 (Service Unavailable)</x:ref>,
     3524         and it is inconvenient or impossible to generate a valid Date.</t>
    35203525
    35213526      <t>If the server does not have a clock that can provide a
     
    37923797  <x:anchor-alias value="Retry-After"/>
    37933798<t>
    3794    The header "Retry-After" field can be used with a 503 (Service
    3795    Unavailable) response to indicate how long the service is expected to
     3799   The header "Retry-After" field can be used with a <x:ref>503 (Service
     3800   Unavailable)</x:ref> response to indicate how long the service is expected to
    37963801   be unavailable to the requesting client. This field &MAY; also be used
    37973802   with any 3xx (Redirection) response to indicate the minimum time the
Note: See TracChangeset for help on using the changeset viewer.