Changeset 1604 for draft-ietf-httpbis/latest/p4-conditional.html

Timestamp:

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

Author:

julian.reschke@…

Message:

replace a few instances of lowercase "must"

File:

• draft-ietf-httpbis/latest/p4-conditional.html (modified) (6 diffs)

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

@@ -460 +460 @@
   } 
   @bottom-center {
-       content: "Expires September 13, 2012"; 
+       content: "Expires September 22, 2012"; 
   } 
   @bottom-right {
@@ -501 +501 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-03-12">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-03-21">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -527 +527 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 13, 2012</td>
+               <td class="left">Expires: September 22, 2012</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -536 +536 @@
             <tr>
                <td class="left"></td>
-               <td class="right">March 12, 2012</td>
+               <td class="right">March 21, 2012</td>
             </tr>
          </tbody>
@@ -566 +566 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 13, 2012.</p>
+      <p>This Internet-Draft will expire on September 22, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -948 +948 @@
 
 <em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7"> 
-         <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct
+         <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
             from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
             (<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.