Ignore:
Timestamp:
Jun 22, 2011, 4:53:33 AM (8 years ago)
Author:
julian.reschke@…
Message:

slightly expand the scope of 503 to include scenarios like rate limiting (see #255)

File:
1 edited

Legend:

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

    r1309 r1310  
    20782078  <iref primary="true" item="Status Codes" subitem="503 Service Unavailable" x:for-anchor=""/>
    20792079<t>
    2080    The server is currently unable to handle the request due to a
    2081    temporary overloading or maintenance of the server. The implication
    2082    is that this is a temporary condition which will be alleviated after
    2083    some delay. If known, the length of the delay &MAY; be indicated in a
    2084    Retry-After header field. If no Retry-After is given, the client &SHOULD;
    2085    handle the response as it would for a 500 response.
     2080   The server is currently unable or unwilling to handle the request due to
     2081   reasons such as temporary overloading, maintenance of the server, or rate
     2082   limiting of the client.
     2083</t>
     2084<t>
     2085   The implication is that this is a temporary condition which will be
     2086   alleviated after some delay. If known, the length of the delay &MAY; be
     2087   indicated in a Retry-After header field (<xref target="header.retry-after"/>).
     2088   If no Retry-After is given, the client &SHOULD; handle the response as it
     2089   would for a 500 response.
    20862090</t>
    20872091<x:note>
     
    41334137  <list style="symbols">
    41344138    <t>
     4139      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/255"/>:
     4140      "Clarify status code for rate limiting"
     4141    </t>
     4142    <t>
    41354143      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/294"/>:
    41364144      "clarify 403 forbidden"
Note: See TracChangeset for help on using the changeset viewer.