Ignore:
Timestamp:
Jun 22, 2012, 12:12:17 AM (7 years ago)
Author:
julian.reschke@…
Message:

Replace "may" by "might" (see #362)

File:
1 edited

Legend:

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

    r1683 r1684  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 23, 2012";
     451       content: "Expires December 24, 2012";
    452452  }
    453453  @bottom-right {
     
    497497      <meta name="dct.creator" content="Reschke, J. F.">
    498498      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    499       <meta name="dct.issued" scheme="ISO8601" content="2012-06-21">
     499      <meta name="dct.issued" scheme="ISO8601" content="2012-06-22">
    500500      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    501501      <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. Furthermore, it defines HTTP message content, metadata, and content negotiation.">
     
    528528            </tr>
    529529            <tr>
    530                <td class="left">Expires: December 23, 2012</td>
     530               <td class="left">Expires: December 24, 2012</td>
    531531               <td class="right">greenbytes</td>
    532532            </tr>
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">June 21, 2012</td>
     535               <td class="right">June 22, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    563563         in progress”.
    564564      </p>
    565       <p>This Internet-Draft will expire on December 23, 2012.</p>
     565      <p>This Internet-Draft will expire on December 24, 2012.</p>
    566566      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    567567      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    858858      <p id="rfc.section.1.2.p.5">Unless noted otherwise, Recipients <em class="bcp14">MUST</em> be able to parse all protocol elements matching the ABNF rules defined for them and <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
    859859         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
    860          different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
    861          Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
    862          error recovery could lead to dangerous consequences.
     860         different error handling strategies; for example, a Web browser might wish to transparently recover from a response where
     861         the Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type
     862         of error recovery could lead to dangerous consequences.
    863863      </p>
    864864      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
Note: See TracChangeset for help on using the changeset viewer.