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

Timestamp:

16/07/12 02:02:32 (9 years ago)

Author:

mnot@…

Message:

Remove redundant text in Vary; fixes #373.

File:

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

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

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires January 16, 2013"; 
+       content: "Expires January 17, 2013"; 
   } 
   @bottom-right {
@@ -491 +491 @@
       <link href="p5-range.html" rel="prev">
       <link href="p7-auth.html" rel="next">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
@@ -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-07-15">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-07-16">
       <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. HTTP has been in use by the World Wide Web global information initiative since 1990. 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.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 16, 2013</td>
+               <td class="left">Expires: January 17, 2013</td>
                <td class="right">M. Nottingham, Editor</td>
             </tr>
@@ -541 +541 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 15, 2012</td>
+               <td class="right">July 16, 2012</td>
             </tr>
          </tbody>
@@ -570 +570 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 16, 2013.</p>
+      <p>This Internet-Draft will expire on January 17, 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>
@@ -1542 +1542 @@
       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
       <p id="rfc.section.7.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
-      <p id="rfc.section.7.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="Using Negotiated Responses">Section&nbsp;4.3</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="Using Negotiated Responses">Section&nbsp;4.3</a>.
+      <p id="rfc.section.7.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="Using Negotiated Responses">Section&nbsp;4.3</a>.
       </p>
       <p id="rfc.section.7.5.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select