Ignore:
Timestamp:
Jan 26, 2012, 6:54:04 AM (8 years ago)
Author:
julian.reschke@…
Message:

spelling & grammar

File:
1 edited

Legend:

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

    r1512 r1514  
    358358  }
    359359  @bottom-center {
    360        content: "Expires July 28, 2012";
     360       content: "Expires July 29, 2012";
    361361  }
    362362  @bottom-right {
     
    410410      <meta name="dct.creator" content="Reschke, J. F.">
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    412       <meta name="dct.issued" scheme="ISO8601" content="2012-01-25">
     412      <meta name="dct.issued" scheme="ISO8601" content="2012-01-26">
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    414414      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
     
    441441            </tr>
    442442            <tr>
    443                <td class="left">Expires: July 28, 2012</td>
     443               <td class="left">Expires: July 29, 2012</td>
    444444               <td class="right">HP</td>
    445445            </tr>
     
    494494            <tr>
    495495               <td class="left"></td>
    496                <td class="right">January 25, 2012</td>
     496               <td class="right">January 26, 2012</td>
    497497            </tr>
    498498         </tbody>
     
    524524         in progress”.
    525525      </p>
    526       <p>This Internet-Draft will expire on July 28, 2012.</p>
     526      <p>This Internet-Draft will expire on July 29, 2012.</p>
    527527      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    528528      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    22282228      </p>
    22292229      <p id="rfc.section.9.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
    2230          when it doesn't convey any useful information (as it is usually the case for requests that do not contain a payload).
     2230         when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload).
    22312231      </p>
    22322232      <p id="rfc.section.9.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
     
    23212321      <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
    23222322      <p id="rfc.section.9.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;6.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;6.2</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
    2323          to trace a request which appears to be failing or looping in mid-chain.
     2323         to trace a request which appears to be failing or looping mid-chain.
    23242324      </p>
    23252325      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
     
    23522352      <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    23532353      <p id="rfc.section.9.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
    2354          to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing
     2354         to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
    23552355         the redirected request.
    23562356      </p>
     
    28312831         of From and Referer information.
    28322832      </p>
    2833       <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.9</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which
    2834          might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
    2835          has no better mechanism.
     2833      <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
     2834         be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently has
     2835         no better mechanism.
    28362836      </p>
    28372837      <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
Note: See TracChangeset for help on using the changeset viewer.