Ignore:
Timestamp:
06/01/13 11:23:55 (10 years ago)
Author:
fielding@…
Message:

delegate cache requirements from 304 to p6; related to #406

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p4-conditional.html

    r2080 r2093  
    449449  }
    450450  @bottom-center {
    451        content: "Expires July 6, 2013";
     451       content: "Expires July 10, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-01-02">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-01-06">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
    … …  
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: July 6, 2013</td>
    520                <td class="right">January 2, 2013</td>
     519               <td class="left">Expires: July 10, 2013</td>
     520               <td class="right">January 6, 2013</td>
    521521            </tr>
    522522         </tbody>
    … …  
    545545         in progress”.
    546546      </p>
    547       <p>This Internet-Draft will expire on July 6, 2013.</p>
     547      <p>This Internet-Draft will expire on July 10, 2013.</p>
    548548      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    549549      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    10661066      <p id="rfc.section.4.1.p.4">Since the goal of a 304 response is to minimize information transfer when the recipient already has one or more cached representations,
    10671067         a sender <em class="bcp14">SHOULD NOT</em> generate representation metadata other than the above listed fields unless said metadata exists for the purpose of guiding
    1068          cache updates (e.g., future HTTP extensions).
    1069       </p>
    1070       <p id="rfc.section.4.1.p.5">If the recipient of a 304 response does not have a cached representation corresponding to the entity-tag indicated by the
    1071          304 response, then the recipient <em class="bcp14">MUST NOT</em> use the 304 to update its own cache. If this conditional request originated with an outbound client, such as a user agent
    1072          with its own cache sending a conditional GET to a shared proxy, then the 304 response <em class="bcp14">MAY</em> be forwarded to that client. Otherwise, the recipient <em class="bcp14">MUST</em> disregard the 304 response and repeat the request without any preconditions.
    1073       </p>
    1074       <p id="rfc.section.4.1.p.6">If a cache uses a received 304 response to update a cache entry, the cache <em class="bcp14">MUST</em> update the entry to reflect any new field values given in the response.
     1068         cache updates (e.g., <a href="#header.last-modified" class="smpl">Last-Modified</a> might be useful if the response does not have an <a href="#header.etag" class="smpl">ETag</a> field).
     1069      </p>
     1070      <p id="rfc.section.4.1.p.5">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Responses with 304 Not Modified">Section 4.2.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
     1071         GET to a shared proxy, then the proxy <em class="bcp14">SHOULD</em> forward the 304 response to that client.
    10751072      </p>
    10761073      <div id="rfc.iref.21"></div>
    … …  
    14521449                     </ul>
    14531450                  </li>
    1454                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#Part6"><b>9.1</b></a></li>
     1451                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#rfc.xref.Part6.4">4.1</a>, <a href="#Part6"><b>9.1</b></a><ul>
     1452                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">4.1</a></li>
     1453                     </ul>
     1454                  </li>
    14551455               </ul>
    14561456            </li>

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2080 r2093  
    2727  <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2828  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     29  <!ENTITY freshening-responses       "<xref target='Part6' x:rel='#freshening.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2930  <!ENTITY header-accept-encoding     "<xref target='Part2' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3031  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    958959   a sender &SHOULD-NOT; generate representation metadata other
    959960   than the above listed fields unless said metadata exists for the
    960    purpose of guiding cache updates (e.g., future HTTP extensions).
    961 </t>
    962 <t>
    963    If the recipient of a 304 response does not have a cached representation
    964    corresponding to the entity-tag indicated by the 304 response, then the
    965    recipient &MUST-NOT; use the 304 to update its own cache.  If this
    966    conditional request originated with an outbound client, such as a user agent
    967    with its own cache sending a conditional GET to a shared proxy, then the 304
    968    response &MAY; be forwarded to that client.  Otherwise, the recipient &MUST;
    969    disregard the 304 response and repeat the request without any preconditions.
    970 </t>
    971 <t>
    972    If a cache uses a received 304 response to update a cache entry, the
    973    cache &MUST; update the entry to reflect any new field values given in
    974    the response.
     961   purpose of guiding cache updates (e.g., <x:ref>Last-Modified</x:ref> might
     962   be useful if the response does not have an <x:ref>ETag</x:ref> field).
     963</t>
     964<t>
     965   Requirements on a cache that receives a 304 response are defined in
     966   &freshening-responses;. If the conditional request originated with an
     967   outbound client, such as a user agent with its own cache sending a
     968   conditional GET to a shared proxy, then the proxy &SHOULD; forward the
     969   304 response to that client.
    975970</t>
    976971</section>
Note: See TracChangeset for help on using the changeset viewer.