* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 827


Ignore:
Timestamp:
2010-06-07 04:29:53 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

Clarify differences between / requirements for request and response CC directives (see #168)

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

Legend:

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

    r826 r827  
    402402      <meta name="dct.creator" content="Reschke, J. F."> 
    403403      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 
    404       <meta name="dct.issued" scheme="ISO8601" content="2010-06-02"> 
     404      <meta name="dct.issued" scheme="ISO8601" content="2010-06-07"> 
    405405      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    406406      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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."> 
     
    428428            </tr> 
    429429            <tr> 
    430                <td class="left">Expires: December 4, 2010</td> 
     430               <td class="left">Expires: December 9, 2010</td> 
    431431               <td class="right">J. Mogul</td> 
    432432            </tr> 
     
    489489            <tr> 
    490490               <td class="left"></td> 
    491                <td class="right">June 2, 2010</td> 
     491               <td class="right">June 7, 2010</td> 
    492492            </tr> 
    493493         </tbody> 
     
    515515         in progress”. 
    516516      </p> 
    517       <p>This Internet-Draft will expire in December 4, 2010.</p> 
     517      <p>This Internet-Draft will expire in December 9, 2010.</p> 
    518518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    519519      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    10301030      <div id="rfc.iref.h.3"></div> 
    10311031      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2> 
    1032       <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. Such cache directives are unidirectional in that the presence of 
    1033          a directive in a request does not imply that the same directive is to be given in the response. 
    1034       </p> 
    1035       <div class="note" id="rfc.section.3.2.p.2">  
     1032      <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives for caches along the request/response chain. Such cache 
     1033         directives are unidirectional in that the presence of a directive in a request does not imply that the same directive is to 
     1034         be given in the response. 
     1035      </p> 
     1036      <p id="rfc.section.3.2.p.2">HTTP/1.1 caches <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled. 
     1037      </p> 
     1038      <div class="note" id="rfc.section.3.2.p.3">  
    10361039         <p> <b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;3.4</a>). 
    10371040         </p>  
    10381041      </div> 
    1039       <p id="rfc.section.3.2.p.3">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives 
     1042      <p id="rfc.section.3.2.p.4">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives 
    10401043         might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific 
    10411044         cache. 
     
    18831886         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>&gt;: "Age calculation" 
    18841887         </li> 
     1888         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>&gt;: "Clarify differences between / requirements for request and response CC directives" 
     1889         </li> 
    18851890         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>&gt;: "IANA registry for cache-control directives" 
    18861891         </li> 
  • draft-ietf-httpbis/latest/p6-cache.xml

    r826 r827  
    977977  <x:anchor-alias value="cache-response-directive"/> 
    978978<t> 
    979   The "Cache-Control" general-header field is used to specify directives that 
    980   &MUST; be obeyed by all caches along the request/response chain. Such cache 
    981   directives are unidirectional in that the presence of a directive in a 
    982   request does not imply that the same directive is to be given in the 
    983   response. 
     979  The "Cache-Control" general-header field is used to specify directives for 
     980  caches along the request/response chain. Such cache directives are 
     981  unidirectional in that the presence of a directive in a request does not 
     982  imply that the same directive is to be given in the response. 
     983</t> 
     984<t> 
     985  HTTP/1.1 caches &MUST; obey the requirements of the Cache-Control directives 
     986  defined in this section. See <xref target="cache.control.extensions"/> for 
     987  information about how Cache-Control directives defined elsewhere are handled. 
    984988</t> 
    985989<x:note> 
     
    24632467    </t> 
    24642468    <t> 
     2469      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/168" />: 
     2470      "Clarify differences between / requirements for request and response CC directives" 
     2471    </t> 
     2472    <t> 
    24652473      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/208" />: 
    24662474      "IANA registry for cache-control directives" 
Note: See TracChangeset for help on using the changeset viewer.