Ignore:
Timestamp:
Oct 30, 2012, 6:39:53 AM (7 years ago)
Author:
julian.reschke@…
Message:

"user-agent" -> "user agent" (see #234)

File:
1 edited

Legend:

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

    r1950 r1957  
    449449  }
    450450  @bottom-center {
    451        content: "Expires April 27, 2013";
     451       content: "Expires May 3, 2013";
    452452  }
    453453  @bottom-right {
     
    496496      <meta name="dct.creator" content="Reschke, J. F.">
    497497      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    498       <meta name="dct.issued" scheme="ISO8601" content="2012-10-24">
     498      <meta name="dct.issued" scheme="ISO8601" content="2012-10-30">
    499499      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    500500      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    524524            <tr>
    525525               <td class="left">Intended status: Standards Track</td>
    526                <td class="right">October 24, 2012</td>
     526               <td class="right">October 30, 2012</td>
    527527            </tr>
    528528            <tr>
    529                <td class="left">Expires: April 27, 2013</td>
     529               <td class="left">Expires: May 3, 2013</td>
    530530               <td class="right"></td>
    531531            </tr>
     
    555555         in progress”.
    556556      </p>
    557       <p>This Internet-Draft will expire on April 27, 2013.</p>
     557      <p>This Internet-Draft will expire on May 3, 2013.</p>
    558558      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    559559      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    12111211      <p id="rfc.section.3.4.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
    12121212         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    1213          a user-agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
     1213         a user agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    12141214         to choose from is very large, reactive negotiation might not be appropriate.
    12151215      </p>
     
    29542954      <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
    29552955      <p id="rfc.section.8.1.3.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
    2956             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.
     2956            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.
    29572957      </p>
    29582958      <p id="rfc.section.8.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>
Note: See TracChangeset for help on using the changeset viewer.