21/03/12 12:30:28 (11 years ago)

replace a few instances of lowercase "must"

1 edited


  • draft-ietf-httpbis/latest/p4-conditional.html

    r1592 r1604  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 13, 2012";
     462       content: "Expires September 22, 2012";
    463463  }
    464464  @bottom-right {
    501501      <meta name="dct.creator" content="Reschke, J. F.">
    502502      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    503       <meta name="dct.issued" scheme="ISO8601" content="2012-03-12">
     503      <meta name="dct.issued" scheme="ISO8601" content="2012-03-21">
    504504      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    505505      <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 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
    527527            </tr>
    528528            <tr>
    529                <td class="left">Expires: September 13, 2012</td>
     529               <td class="left">Expires: September 22, 2012</td>
    530530               <td class="right">J. Reschke, Editor</td>
    531531            </tr>
    536536            <tr>
    537537               <td class="left"></td>
    538                <td class="right">March 12, 2012</td>
     538               <td class="right">March 21, 2012</td>
    539539            </tr>
    540540         </tbody>
    566566         in progress”.
    567567      </p>
    568       <p>This Internet-Draft will expire on September 13, 2012.</p>
     568      <p>This Internet-Draft will expire on September 22, 2012.</p>
    569569      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    570570      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    949949<em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7">
    950          <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct
     950         <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct
    951951            from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
    952952            (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
Note: See TracChangeset for help on using the changeset viewer.