Ignore:
Timestamp:
May 31, 2011, 12:33:19 AM (8 years ago)
Author:
julian.reschke@…
Message:

consistency: behaviour->behavior

File:
1 edited

Legend:

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

    r1291 r1302  
    362362  }
    363363  @bottom-center {
    364        content: "Expires November 28, 2011";
     364       content: "Expires December 2, 2011";
    365365  }
    366366  @bottom-right {
     
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-05-27">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-05-31">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <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.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: November 28, 2011</td>
     436               <td class="left">Expires: December 2, 2011</td>
    437437               <td class="right">J. Mogul</td>
    438438            </tr>
     
    495495            <tr>
    496496               <td class="left"></td>
    497                <td class="right">May 27, 2011</td>
     497               <td class="right">May 31, 2011</td>
    498498            </tr>
    499499         </tbody>
     
    523523         in progress”.
    524524      </p>
    525       <p>This Internet-Draft will expire on November 28, 2011.</p>
     525      <p>This Internet-Draft will expire on December 2, 2011.</p>
    526526      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    527527      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    770770      </p>
    771771      <p id="rfc.section.2.1.p.3">In this context, a cache has "understood" a request method or a response status code if it recognises it and implements any
    772          cache-specific behaviour. In particular, 206 Partial Content responses cannot be cached by an implementation that does not
     772         cache-specific behavior. In particular, 206 Partial Content responses cannot be cached by an implementation that does not
    773773         handle partial content (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Partial and Incomplete Responses">Section&nbsp;2.1.1</a>).
    774774      </p>
Note: See TracChangeset for help on using the changeset viewer.