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

Timestamp:

03/02/09 11:03:36 (13 years ago)

Author:

julian.reschke@…

Message:

reorganize header introductions consistent (related to #36, see also [364])

File:

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

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

@@ -486 +486 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">February 2, 2009</td>
+            <td class="header right">February 3, 2009</td>
          </tr>
       </table>
@@ -1572 +1572 @@
       <div id="rfc.iref.h.4"></div>
       <h2 id="rfc.section.15.3"><a href="#rfc.section.15.3">15.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
-      <p id="rfc.section.15.3.p.1">The Expires entity-header field gives the date/time after which the response is considered stale. A stale cache entry may
+      <p id="rfc.section.15.3.p.1">The entity-header field "Expires" gives the date/time after which the response is considered stale. A stale cache entry may
          not normally be returned by a cache (either a proxy cache or a user agent cache) unless it is first validated with the origin
          server (or with an intermediate cache that has a fresh copy of the entity). See <a href="#expiration.model" title="Expiration Model">Section&nbsp;3</a> for further discussion of the expiration model.