* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1310


Ignore:
Timestamp:
2011-06-22 04:53:33 (4 years ago)
Author:
julian.reschke@gmx.de
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r1309 r1310  
    19351935      <div id="rfc.iref.s.41"></div> 
    19361936      <h3 id="rfc.section.8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3> 
    1937       <p id="rfc.section.8.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication 
    1938          is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response. 
    1939       </p> 
    1940       <div class="note" id="rfc.section.8.5.4.p.2">  
     1937      <p id="rfc.section.8.5.4.p.1">The server is currently unable or unwilling to handle the request due to reasons such as temporary overloading, maintenance 
     1938         of the server, or rate limiting of the client. 
     1939      </p> 
     1940      <p id="rfc.section.8.5.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the 
     1941         delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response. 
     1942      </p> 
     1943      <div class="note" id="rfc.section.8.5.4.p.3">  
    19411944         <p> <b>Note:</b> The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers might 
    19421945            wish to simply refuse the connection. 
     
    25082511                  <td class="left">http</td> 
    25092512                  <td class="left">standard</td> 
    2510                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>  
     2513                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;9.7</a>  
    25112514                  </td> 
    25122515               </tr> 
     
    30483051      <p id="rfc.section.C.16.p.1">Closed issues: </p> 
    30493052      <ul> 
     3053         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>&gt;: "Clarify status code for rate limiting" 
     3054         </li> 
    30503055         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/294">http://tools.ietf.org/wg/httpbis/trac/ticket/294</a>&gt;: "clarify 403 forbidden" 
    30513056         </li> 
     
    31703175                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">3</a>, <a href="#rfc.xref.header.max-forwards.2">7.2</a>, <a href="#rfc.xref.header.max-forwards.3">7.8</a>, <a href="#rfc.iref.h.6"><b>9.5</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li> 
    31713176                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3</a>, <a href="#rfc.iref.h.7"><b>9.6</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 
    3172                         <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">5</a>, <a href="#rfc.iref.h.8"><b>9.7</b></a>, <a href="#rfc.xref.header.retry-after.2">10.3</a></li> 
     3177                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">5</a>, <a href="#rfc.xref.header.retry-after.2">8.5.4</a>, <a href="#rfc.iref.h.8"><b>9.7</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li> 
    31733178                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">5</a>, <a href="#rfc.iref.h.9"><b>9.8</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">A</a></li> 
    31743179                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3</a>, <a href="#rfc.iref.h.10"><b>9.9</b></a>, <a href="#rfc.xref.header.user-agent.2">10.3</a>, <a href="#rfc.xref.header.user-agent.3">11.1</a></li> 
     
    32823287            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 
    32833288                  <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3</a>, <a href="#rfc.iref.r.1"><b>9.6</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 
    3284                   <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">5</a>, <a href="#rfc.iref.r.2"><b>9.7</b></a>, <a href="#rfc.xref.header.retry-after.2">10.3</a></li> 
     3289                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">5</a>, <a href="#rfc.xref.header.retry-after.2">8.5.4</a>, <a href="#rfc.iref.r.2"><b>9.7</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li> 
    32853290                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">8.3.3</a>, <a href="#RFC1945"><b>13.2</b></a><ul> 
    32863291                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">8.3.3</a></li> 
  • 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.