Changeset 732 for draft-ietf-httpbis/latest

Timestamp:

Dec 7, 2009, 9:46:53 AM (10 years ago)

Author:

julian.reschke@…

Message:

typos fixed (editorial change)

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (8 diffs)
• p6-cache.xml (modified) (4 diffs)

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

@@ -402 +402 @@
       <meta name="DC.Creator" content="Reschke, J. F.">
       <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-01">
+      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-07">
       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
       <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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.">
@@ -435 +435 @@
             </tr>
             <tr>
-               <td class="left">Expires: June 4, 2010</td>
+               <td class="left">Expires: June 10, 2010</td>
                <td class="right">HP</td>
             </tr>
@@ -492 +492 @@
             <tr>
                <td class="left"></td>
-               <td class="right">December 1, 2009</td>
+               <td class="right">December 7, 2009</td>
             </tr>
          </tbody>
@@ -522 +522 @@
       <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
       </p>
-      <p>This Internet-Draft will expire in June 4, 2010.</p>
+      <p>This Internet-Draft will expire in June 10, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -771 +771 @@
       <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, caches <em class="bcp14">MUST</em> include a single Age header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;3.1</a>) in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>. <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: DISCUSS: this currently includes successfully validated responses.]</span> 
       </p>
-      <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., A cache must not reply to such a request before having forwarded
+      <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., a cache must not reply to such a request before having forwarded
          the request and having received a corresponding response.
       </p>
@@ -1111 +1111 @@
          <li> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
             content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
-            directive was recieved; i.e., the special handling for the qualified form is not widely implemented.
+            directive was received; i.e., the special handling for the qualified form is not widely implemented.
          </li>
       </ul>
@@ -1249 +1249 @@
       <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
       <p id="rfc.section.3.5.p.1">The "Vary" response-header field conveys the set of request-header fields that were used to select the representation.</p>
-      <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisdy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
+      <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
          without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.6</a>.
       </p>
@@ -1278 +1278 @@
       </p>
       <p id="rfc.section.3.6.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status
-         code, distinguish these responses from true failures.
+         code, distinguishes these responses from true failures.
       </p>
       <p id="rfc.section.3.6.p.3">Warning headers can in general be applied to any message, however some warn-codes are specific to caches and can only be applied

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

@@ -495 +495 @@
 <t>
   Requests with methods that are unsafe (&safe-methods;) &MUST; be written through the cache to
-  the origin server; i.e., A cache must not reply to such a request before having forwarded the request and having received a
+  the origin server; i.e., a cache must not reply to such a request before having forwarded the request and having received a
   corresponding response.
 </t>
@@ -1104 +1104 @@
       be stored, and cannot ensure the privacy of the message content.
       Also, private response directives with field-names are often handled by
-      implementations as if an unqualified private directive was recieved; i.e.,
+      implementations as if an unqualified private directive was received; i.e.,
       the special handling for the qualified form is not widely implemented.
 </t>
@@ -1345 +1345 @@
 <t>
   Caches use this information, in part, to determine whether a stored response
-  can be used to satisdy a given request; see
+  can be used to satisfy a given request; see
   <xref target="caching.negotiated.responses" />.
   determines, while the response is fresh, whether a cache is permitted to use the
@@ -1403 +1403 @@
 <t>
   Warnings can be used for other purposes, both cache-related and otherwise. The use of a
-  warning, rather than an error status code, distinguish these responses from true failures.
+  warning, rather than an error status code, distinguishes these responses from true failures.
 </t>
 <t>