Ignore:
Timestamp:
Nov 12, 2012, 1:14:42 AM (7 years ago)
Author:
julian.reschke@…
Message:

editorial clarification

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r1976 r1991  
    452452  }
    453453  @bottom-center {
    454        content: "Expires May 10, 2013";
     454       content: "Expires May 16, 2013";
    455455  }
    456456  @bottom-right {
     
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2012-11-06">
     500      <meta name="dct.issued" scheme="ISO8601" content="2012-11-12">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <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.">
     
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: May 10, 2013</td>
     526               <td class="left">Expires: May 16, 2013</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
     
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">November 6, 2012</td>
     535               <td class="right">November 12, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on May 10, 2013.</p>
     561      <p>This Internet-Draft will expire on May 16, 2013.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    905905      </p>
    906906      <p id="rfc.section.4.1.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past
    907          to indicate that the response is already stale. Compliant caches will normally validate the cached response before reusing
     907         to indicate that the response is already stale. Compliant caches will normally validate a stale cached response before reusing
    908908         it for subsequent requests (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section&nbsp;4.1.4</a>).
    909909      </p>
Note: See TracChangeset for help on using the changeset viewer.