Changeset 697 for draft-ietf-httpbis/latest/p6-cache.html

Timestamp:

Sep 25, 2009, 7:43:16 AM (10 years ago)

Author:

julian.reschke@…

Message:

editorial: rephrase header introductions ("the *-header field 'foobar'" -> "the "foobar" *-header field")

File:

• draft-ietf-httpbis/latest/p6-cache.html (modified) (9 diffs)

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

@@ -398 +398 @@
       <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-09-16">
+      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-25">
       <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.">
@@ -430 +430 @@
          </tr>
          <tr>
-            <td class="header left">Expires: March 20, 2010</td>
+            <td class="header left">Expires: March 29, 2010</td>
             <td class="header right">HP</td>
          </tr>
@@ -487 +487 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">September 16, 2009</td>
+            <td class="header right">September 25, 2009</td>
          </tr>
       </table>
@@ -511 +511 @@
       <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 March 20, 2010.</p>
+      <p>This Internet-Draft will expire in March 29, 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>
@@ -974 +974 @@
       <div id="rfc.iref.h.2"></div>
       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
-      <p id="rfc.section.3.1.p.1">The response-header field "Age" conveys the sender's estimate of the amount of time since the response (or its validation)
+      <p id="rfc.section.3.1.p.1">The "Age" response-header field conveys the sender's estimate of the amount of time since the response (or its validation)
          was generated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
       </p>
@@ -992 +992 @@
       <div id="rfc.iref.h.3"></div>
       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
-      <p id="rfc.section.3.2.p.1">The general-header field "Cache-Control" is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from
+      <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. The directives specify behavior intended to prevent caches from
          adversely interfering with the request or response. Cache directives are unidirectional in that the presence of a directive
          in a request does not imply that the same directive is to be given in the response.
@@ -1195 +1195 @@
       <div id="rfc.iref.h.4"></div>
       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
-      <p id="rfc.section.3.3.p.1">The entity-header field "Expires" gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
+      <p id="rfc.section.3.3.p.1">The "Expires" entity-header field gives the date/time after which the response is considered stale. See <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a> for further discussion of the freshness model.
       </p>
       <p id="rfc.section.3.3.p.2">The presence of an Expires field does not imply that the original resource will change or cease to exist at, before, or after
@@ -1217 +1217 @@
       <div id="rfc.iref.h.5"></div>
       <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
-      <p id="rfc.section.3.4.p.1">The general-header field "Pragma" is used to include implementation-specific directives that might apply to any recipient
+      <p id="rfc.section.3.4.p.1">The "Pragma" general-header field is used to include implementation-specific directives that might apply to any recipient
          along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however,
          some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
@@ -1261 +1261 @@
       <div id="rfc.iref.h.7"></div>
       <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
-      <p id="rfc.section.3.6.p.1">The general-header field "Warning" is used to carry additional information about the status or transformation of a message
+      <p id="rfc.section.3.6.p.1">The "Warning" general-header field is used to carry additional information about the status or transformation of a message
          that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced
          by caching operations or transformations applied to the entity body of the message.