Changeset 2107


Ignore:
Timestamp:
Jan 10, 2013, 10:19:24 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) fix jumbled description of Retry-After

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

Legend:

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

    r2106 r2107  
    29862986      <div id="rfc.iref.r.3"></div>
    29872987      <h3 id="rfc.section.7.1.3"><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
    2988       <p id="rfc.section.7.1.3.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
    2989             Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user agent is asked to wait before issuing the redirected request.
     2988      <p id="rfc.section.7.1.3.p.1">Servers send the "Retry-After" header field to indicate how long the user agent ought to wait before making a follow-up request.
     2989         When sent with a <a href="#status.503" class="smpl">503 (Service Unavailable)</a> response, Retry-After indicates how long the service is expected to be unavailable to the client. When sent with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response, Retry-After indicates the minimum time that the user agent is asked to wait before issuing the redirected request.
    29902990      </p>
    29912991      <p id="rfc.section.7.1.3.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2106 r2107  
    38343834  <x:anchor-alias value="Retry-After"/>
    38353835<t>
    3836    The header "Retry-After" field can be used with a <x:ref>503 (Service
    3837    Unavailable)</x:ref> response to indicate how long the service is expected to
    3838    be unavailable to the requesting client. This field &MAY; also be used
    3839    with any <x:ref>3xx (Redirection)</x:ref> response to indicate the minimum time the
    3840    user agent is asked to wait before issuing the redirected request.
     3836   Servers send the "Retry-After" header field to indicate how long the user
     3837   agent ought to wait before making a follow-up request. When sent with a
     3838   <x:ref>503 (Service Unavailable)</x:ref> response, Retry-After indicates
     3839   how long the service is expected to be unavailable to the client.
     3840   When sent with any <x:ref>3xx (Redirection)</x:ref> response, Retry-After
     3841   indicates the minimum time that the user agent is asked to wait before
     3842   issuing the redirected request.
    38413843</t>
    38423844<t>
Note: See TracChangeset for help on using the changeset viewer.