Changeset 1664


Ignore:
Timestamp:
May 31, 2012, 4:57:29 AM (7 years ago)
Author:
mnot@…
Message:

Note that headers listed in private and no-cache response CC are case-insensitive and not restricted; fixes #355

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

Legend:

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

    r1663 r1664  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 24, 2012";
     465       content: "Expires December 2, 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.576, 2012-05-02 14:26:45, 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.576, 2012-05-02 14:26:45, 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.">
     
    505505      <meta name="dct.creator" content="Reschke, J. F.">
    506506      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    507       <meta name="dct.issued" scheme="ISO8601" content="2012-05-23">
     507      <meta name="dct.issued" scheme="ISO8601" content="2012-05-31">
    508508      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    509509      <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.">
     
    531531            </tr>
    532532            <tr>
    533                <td class="left">Expires: November 24, 2012</td>
     533               <td class="left">Expires: December 2, 2012</td>
    534534               <td class="right">M. Nottingham, Editor</td>
    535535            </tr>
     
    548548            <tr>
    549549               <td class="left"></td>
    550                <td class="right">May 23, 2012</td>
     550               <td class="right">May 31, 2012</td>
    551551            </tr>
    552552         </tbody>
     
    578578         in progress”.
    579579      </p>
    580       <p>This Internet-Draft will expire on November 24, 2012.</p>
     580      <p>This Internet-Draft will expire on December 2, 2012.</p>
    581581      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    582582      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    13341334            with the listed response header fields. That is, a shared cache <em class="bcp14">MUST NOT</em> store the specified field-names(s), whereas it <em class="bcp14">MAY</em> store the remainder of the response message.
    13351335         </li>
     1336         <li>The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     1337            case-insensitive.
     1338         </li>
    13361339         <li> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
    13371340            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
     
    13501353            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
    13511354            server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
     1355         </li>
     1356         <li>The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     1357            case-insensitive.
    13521358         </li>
    13531359         <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

    r1663 r1664  
    13771377      the specified field-names(s), whereas it &MAY; store the remainder of the
    13781378      response message.</t>
     1379      <t>The field-names given are not limited to the set of standard header
     1380      fields defined by this specification. Field names are case-insensitive.
     1381      </t>
    13791382      <t> <x:h>Note:</x:h> This usage of the word "private" only controls
    13801383      where the response can be stored; it cannot ensure the privacy of the
     
    14031406      re-use of certain header fields in a response, while still allowing
    14041407      caching of the rest of the response.</t>
     1408      <t>The field-names given are not limited to the set of standard header
     1409      fields defined by this specification. Field names are case-insensitive.
     1410      </t>
    14051411      <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey
    14061412      this directive. Also, no-cache response directives with field-names are
Note: See TracChangeset for help on using the changeset viewer.