Changeset 1551 for draft-ietf-httpbis/latest

Timestamp:

Feb 28, 2012, 12:46:57 AM (8 years ago)

Author:

fielding@…

Message:

make entities out of a MAY and MUST NOT

Location:

draft-ietf-httpbis/latest

Files:

• p4-conditional.html (modified) (6 diffs)
• p4-conditional.xml (modified) (1 diff)
• p6-cache.html (modified) (6 diffs)
• p6-cache.xml (modified) (1 diff)

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

@@ -460 +460 @@
   } 
   @bottom-center {
-       content: "Expires August 24, 2012"; 
+       content: "Expires August 31, 2012"; 
   } 
   @bottom-right {
@@ -507 +507 @@
       <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-02-21">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-02-28">
       <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.">
@@ -533 +533 @@
             </tr>
             <tr>
-               <td class="left">Expires: August 24, 2012</td>
+               <td class="left">Expires: August 31, 2012</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -590 +590 @@
             <tr>
                <td class="left"></td>
-               <td class="right">February 21, 2012</td>
+               <td class="right">February 28, 2012</td>
             </tr>
          </tbody>
@@ -620 +620 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on August 24, 2012.</p>
+      <p>This Internet-Draft will expire on August 31, 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>
@@ -1093 +1093 @@
          at least one of those representations matches the selected representation.
       </p>
-      <p id="rfc.section.3.2.p.2">If-None-Match MAY also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
-         an existing representation of the target resource when the client believes that the resource does not have a current representation.
-         This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation
+      <p id="rfc.section.3.2.p.2">If-None-Match <em class="bcp14">MAY</em> also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying an existing
+         representation of the target resource when the client believes that the resource does not have a current representation. This
+         is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation
          for the target resource.
       </p>

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

@@ -888 +888 @@
 </t>
 <t>
-   If-None-Match MAY also be used with a value of "*" to prevent an unsafe
+   If-None-Match &MAY; also be used with a value of "*" to prevent an unsafe
    request method (e.g., PUT) from inadvertently modifying an existing
    representation of the target resource when the client believes that

draft-ietf-httpbis/latest/p6-cache.html

@@ -463 +463 @@
   } 
   @bottom-center {
-       content: "Expires August 24, 2012"; 
+       content: "Expires August 31, 2012"; 
   } 
   @bottom-right {
@@ -511 +511 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-02-21">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-02-28">
       <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 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -537 +537 @@
             </tr>
             <tr>
-               <td class="left">Expires: August 24, 2012</td>
+               <td class="left">Expires: August 31, 2012</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -602 +602 @@
             <tr>
                <td class="left"></td>
-               <td class="right">February 21, 2012</td>
+               <td class="right">February 28, 2012</td>
             </tr>
          </tbody>
@@ -632 +632 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on August 24, 2012.</p>
+      <p>This Internet-Draft will expire on August 31, 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>
@@ -1396 +1396 @@
       </p>
       <ul class="empty">
-         <li>The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful
-            validation on the origin server. This allows an origin server to prevent a cache from using it to satisfy a request without
-            contacting it, even by caches that have been configured to return stale responses.
+         <li>The no-cache response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
+            prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return
+            stale responses.
          </li>
          <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated

draft-ietf-httpbis/latest/p6-cache.xml

@@ -1447 +1447 @@
    <iref item="no-cache" primary="true" subitem="Cache Directive" />
    <list>
-      <t>The no-cache response directive indicates that the response MUST NOT
+      <t>The no-cache response directive indicates that the response &MUST-NOT;
       be used to satisfy a subsequent request without successful validation on
       the origin server. This allows an origin server to prevent a cache from