Changeset 1945

Timestamp:

22/10/12 15:42:34 (8 years ago)

Author:

julian.reschke@…

Message:

fix typos

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (7 diffs)
• p6-cache.xml (modified) (2 diffs)

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

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires April 6, 2013"; 
+       content: "Expires April 25, 2013"; 
   } 
   @bottom-right {
@@ -498 +498 @@
       <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-10-03">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-10-22">
       <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. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 6, 2013</td>
+               <td class="left">Expires: April 25, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 3, 2012</td>
+               <td class="right">October 22, 2012</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 6, 2013.</p>
+      <p>This Internet-Draft will expire on April 25, 2013.</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>
@@ -1431 +1431 @@
       </p>
       <div class="note" id="rfc.section.7.3.p.7"> 
-         <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), that directive overrides the Expires field. Likewise, the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) overrides the <a href="#header.expires" class="smpl">Expires</a> header fieldin shared caches.
+         <p> <b>Note:</b> If a response includes a <a href="#header.cache-control" class="smpl">Cache-Control</a> field with the max-age directive (see <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.7</a>), that directive overrides the Expires field. Likewise, the s-maxage directive (<a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.8</a>) overrides the <a href="#header.expires" class="smpl">Expires</a> header field in shared caches.
          </p> 
       </div>
@@ -1791 +1791 @@
       </p>
       <p id="rfc.section.10.p.3">Likewise, implementation flaws (as well as misunderstanding of cache operation) might lead to caching of sensitive information
-         (e.g., authentication credentials) that is thought to be private, exposing it to unauthorised parties.
+         (e.g., authentication credentials) that is thought to be private, exposing it to unauthorized parties.
       </p>
       <p id="rfc.section.10.p.4">Note that the Set-Cookie response header <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a> does not inhibit caching; a cacheable response with a Set-Cookie header can be (and often is) used to satisfy subsequent requests

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

@@ -1619 +1619 @@
        that directive overrides the Expires field. Likewise, the s-maxage
        directive (<xref target="cache-response-directive.s-maxage" />) overrides
-       the <x:ref>Expires</x:ref> header fieldin shared caches.
+       the <x:ref>Expires</x:ref> header field in shared caches.
    </t>
 </x:note>
@@ -2099 +2099 @@
    operation) might lead to caching of sensitive information (e.g.,
    authentication credentials) that is thought to be private, exposing it to
-   unauthorised parties.
+   unauthorized parties.
 </t>
 <t>