Changeset 2487


Ignore:
Timestamp:
Nov 11, 2013, 12:22:08 PM (6 years ago)
Author:
fielding@…
Message:

206 is also cacheable by default, so be consistent with [2482] to say that; see #432

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2485 r2487  
    23062306               protocol.
    23072307            </p>
    2308             <p id="rfc.section.6.1.p.2">Responses with status codes that are defined as cacheable by default (e.g., 200, 203, 204, 300, 301, 404, 405, 410, 414, 501
    2309                in this specification) can be reused by a cache with heuristic expiration unless otherwise indicated by the method definition
     2308            <p id="rfc.section.6.1.p.2">Responses with status codes that are defined as cacheable by default (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414,
     2309               501 in this specification) can be reused by a cache with heuristic expiration unless otherwise indicated by the method definition
    23102310               or explicit cache controls <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>; all other status codes are not cacheable by default.
    23112311            </p>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2485 r2487  
    26532653<t>
    26542654   Responses with status codes that are defined as cacheable by default
    2655    (e.g., 200, 203, 204, 300, 301, 404, 405, 410, 414, 501 in this
     2655   (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501 in this
    26562656   specification) can be reused by a cache with heuristic expiration unless
    26572657   otherwise indicated by the method definition or explicit cache controls
  • draft-ietf-httpbis/latest/p5-range.html

    r2480 r2487  
    445445  }
    446446  @bottom-center {
    447        content: "Expires May 11, 2014";
     447       content: "Expires May 15, 2014";
    448448  }
    449449  @bottom-right {
     
    488488      <meta name="dct.creator" content="Reschke, J. F.">
    489489      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    490       <meta name="dct.issued" scheme="ISO8601" content="2013-11-07">
     490      <meta name="dct.issued" scheme="ISO8601" content="2013-11-11">
    491491      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    492492      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    514514            </tr>
    515515            <tr>
    516                <td class="left">Expires: May 11, 2014</td>
     516               <td class="left">Expires: May 15, 2014</td>
    517517               <td class="right">J. Reschke, Editor</td>
    518518            </tr>
     
    523523            <tr>
    524524               <td class="left"></td>
    525                <td class="right">November 7, 2013</td>
     525               <td class="right">November 11, 2013</td>
    526526            </tr>
    527527         </tbody>
     
    549549            in progress”.
    550550         </p>
    551          <p>This Internet-Draft will expire on May 11, 2014.</p>
     551         <p>This Internet-Draft will expire on May 15, 2014.</p>
    552552      </div>
    553553      <div id="rfc.copyrightnotice">
     
    865865               a prior response containing those header fields. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the representation header fields that would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request.
    866866            </p>
    867             <p id="rfc.section.4.1.p.12">A 206 response is cacheable unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     867            <p id="rfc.section.4.1.p.12">A 206 response is cacheable by default; i.e., unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    868868            </p>
    869869         </div>
  • draft-ietf-httpbis/latest/p5-range.xml

    r2480 r2487  
    618618</t>
    619619<t>
    620    A 206 response is cacheable unless otherwise indicated by
     620   A 206 response is cacheable by default; i.e., unless otherwise indicated by
    621621   explicit cache controls (see &p6-heuristic;).
    622622</t>
Note: See TracChangeset for help on using the changeset viewer.