Changeset 1310 for draft-ietf-httpbis/latest/p2-semantics.xml

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:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -2078 +2078 @@
   <iref primary="true" item="Status Codes" subitem="503 Service Unavailable" x:for-anchor=""/>
 <t>
-   The server is currently unable to handle the request due to a
-   temporary overloading or maintenance of the server. The implication
-   is that this is a temporary condition which will be alleviated after
-   some delay. If known, the length of the delay &MAY; be indicated in a
-   Retry-After header field. If no Retry-After is given, the client &SHOULD;
-   handle the response as it would for a 500 response.
+   The server is currently unable or unwilling to handle the request due to 
+   reasons such as temporary overloading, maintenance of the server, or rate
+   limiting of the client.
+</t>
+<t>
+   The implication is that this is a temporary condition which will be
+   alleviated after some delay. If known, the length of the delay &MAY; be
+   indicated in a Retry-After header field (<xref target="header.retry-after"/>).
+   If no Retry-After is given, the client &SHOULD; handle the response as it
+   would for a 500 response.
 </t>
 <x:note>
@@ -4133 +4137 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/255"/>:
+      "Clarify status code for rate limiting"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/294"/>:
       "clarify 403 forbidden"