Changeset 1563


Ignore:
Timestamp:
Mar 5, 2012, 5:40:47 PM (8 years ago)
Author:
mnot@…
Message:

Adjust language around no-cache with arguments; #337

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r1560 r1563  
    463463  }
    464464  @bottom-center {
    465        content: "Expires September 5, 2012";
     465       content: "Expires September 7, 2012";
    466466  }
    467467  @bottom-right {
     
    498498      <link href="p5-range.html" rel="prev">
    499499      <link href="p7-auth.html" rel="next">
    500       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     500      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
    501501      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    502502      <meta name="dct.creator" content="Fielding, R.">
     
    511511      <meta name="dct.creator" content="Reschke, J. F.">
    512512      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    513       <meta name="dct.issued" scheme="ISO8601" content="2012-03-04">
     513      <meta name="dct.issued" scheme="ISO8601" content="2012-03-06">
    514514      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    515515      <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.">
     
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: September 5, 2012</td>
     539               <td class="left">Expires: September 7, 2012</td>
    540540               <td class="right">J. Mogul</td>
    541541            </tr>
     
    602602            <tr>
    603603               <td class="left"></td>
    604                <td class="right">March 4, 2012</td>
     604               <td class="right">March 6, 2012</td>
    605605            </tr>
    606606         </tbody>
     
    632632         in progress”.
    633633      </p>
    634       <p>This Internet-Draft will expire on September 5, 2012.</p>
     634      <p>This Internet-Draft will expire on September 7, 2012.</p>
    635635      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    636636      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    14191419            stale responses.
    14201420         </li>
    1421          <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
    1422             with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.
    1423             This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of
    1424             the rest of the response.
     1421         <li>If the no-cache response directive specifies one or more field-names, then a cache MAY use the response to satisfy a subsequent
     1422            request, subject to any other restrictions on caching. However, any header fields in the response that have the field-name(s)
     1423            listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin
     1424            server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    14251425         </li>
    14261426         <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1560 r1563  
    14851485      have been configured to return stale responses.</t>
    14861486      <t>If the no-cache response directive specifies one or more field-names,
    1487       this requirement is limited to the field-values associated with the
    1488       listed response header fields. That is, a cache &MUST-NOT; send the
    1489       specified field-name(s) in the response to a subsequent request without successful
    1490       validation on the origin server. This allows an origin server to prevent
    1491       the re-use of certain header fields in a response, while still allowing
    1492       caching of the rest of the response.</t>
     1487      then a cache MAY use the response to satisfy a subsequent request,
     1488      subject to any other restrictions on caching. However, any header fields
     1489      in the response that have the field-name(s) listed &MUST-NOT; be sent
     1490      in the response to a subsequent request without successful revalidation
     1491      with the origin server. This allows an origin server to prevent the
     1492      re-use of certain header fields in a response, while still allowing
     1493      caching of the rest of the response.</t>
    14931494      <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey
    14941495      this directive. Also, no-cache response directives with field-names are
    14951496      often handled by implementations as if an unqualified no-cache directive
    14961497      was received; i.e., the special handling for the qualified form is not
    1497       widely implemented. </t>
     1498      widely implemented.</t>
    14981499   </list>
    14991500</t>
Note: See TracChangeset for help on using the changeset viewer.