Changeset 1287

Timestamp:

20/05/11 07:06:38 (10 years ago)

Author:

julian.reschke@…

Message:

editorial: remove tabs, tune markup, regen HTML

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p6-cache.html (modified) (3 diffs)
• p6-cache.xml (modified) (7 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires November 20, 2011"; 
+       content: "Expires November 21, 2011"; 
   } 
   @bottom-right {
@@ -409 +409 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-05-19">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-05-20">
       <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, hypermedia 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.">
@@ -440 +440 @@
             </tr>
             <tr>
-               <td class="left">Expires: November 20, 2011</td>
+               <td class="left">Expires: November 21, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -493 +493 @@
             <tr>
                <td class="left"></td>
-               <td class="right">May 19, 2011</td>
+               <td class="right">May 20, 2011</td>
             </tr>
          </tbody>
@@ -522 +522 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on November 20, 2011.</p>
+      <p>This Internet-Draft will expire on November 21, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>

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

@@ -837 +837 @@
          with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>.
       </p>
-      <p id="rfc.section.2.3.p.8"> <span class="comment" id="ISSUE-no-req-for-directives">[<a href="#ISSUE-no-req-for-directives" class="smpl">ISSUE-no-req-for-directives</a>: there are not requirements directly applying to cache-request-directives and freshness.]</span> 
-      </p>
-      <p id="rfc.section.2.3.p.9">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
+      <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
          a resource. See <a href="#history.lists" title="History Lists">Section&nbsp;4</a> for an explanation of the difference between caches and history mechanisms.
       </p>
@@ -1266 +1264 @@
          it will also see and understand the private directive and thus default to the safe behavior.
       </p>
-      <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> be ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
+      <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
          will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
          minimally correct even if the cache does not understand the extension(s).
@@ -1324 +1322 @@
 Cache-Control: max-age=30
 Pragma: no-cache
+
 </pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
          understand Cache-Control from serving a cached response.
       </p>
       <div class="note" id="rfc.section.3.4.p.8"> 
-         <p>Note: Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement
-            for "Cache-Control: no-cache" in them.
+         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
+            no-cache" in them.
          </p> 
       </div>

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

@@ -1498 +1498 @@
    <x:anchor-alias value="pragma-directive"/>
 <t>
-         The "Pragma" header field allows backwards compatibility with HTTP/1.0
+   The "Pragma" header field allows backwards compatibility with HTTP/1.0
    caches, so that clients can specify a "no-cache" request that they will
    understand (as Cache-Control was not defined until HTTP/1.1). When the
@@ -1505 +1505 @@
 </t>
 <t>
-         In HTTP/1.0, Pragma was defined as an extensible field for
+   In HTTP/1.0, Pragma was defined as an extensible field for
    implementation-specified directives for recipients. This specification
    deprecates such extensions to improve interoperability.
@@ -1515 +1515 @@
 </artwork></figure>
 <t>
-         When the Cache-Control header is not present in a request, the no-cache
+   When the Cache-Control header is not present in a request, the no-cache
    request pragma-directive &MUST; have the same effect on caches as if
    "Cache-Control: no-cache" were present (see <xref
@@ -1527 +1527 @@
 </t>
 <figure>
-<artwork type="code">
+<artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
 GET / HTTP/1.1
 Host: www.example.com
 Cache-Control: max-age=30
 Pragma: no-cache
+
 </artwork>
 </figure>
@@ -1541 +1542 @@
 <x:note>
    <t>
-      Note: Because the meaning of "Pragma: no-cache" in responses is not
+      <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" in responses is not
       specified, it does not provide a reliable replacement for
       "Cache-Control: no-cache" in them.
-         </t>
+   </t>
 </x:note>
 </section>
@@ -2601 +2602 @@
       "Clarify differences between / requirements for request and response CC directives"
     </t>
-        <t>
-                <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/174" />:
-                "Caching authenticated responses"
-        </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/174" />:
+      "Caching authenticated responses"
+    </t>
     <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/208" />:
@@ -2696 +2697 @@
 <t>
   Closed issues:
-        <list style="symbols">
-                <t>
-                        <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/292"/>:
-                        "Pragma"
-                </t>
-        </list>
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/292"/>:
+      "Pragma"
+    </t>
+  </list>
 </t>
 </section>