Changeset 2375 for draft-ietf-httpbis


Ignore:
Timestamp:
12/09/13 03:02:38 (7 years ago)
Author:
mnot@…
Message:

update HTML

File:
1 edited

Legend:

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

    r2372 r2375  
    446446  }
    447447  @bottom-center {
    448        content: "Expires March 11, 2014";
     448       content: "Expires March 16, 2014";
    449449  }
    450450  @bottom-right {
     
    486486      <link href="p1-messaging.html" rel="prev">
    487487      <link href="p4-conditional.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.599, 2013/08/29 10:34:28, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.599, 2013/08/29 10:34:28, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-09-07">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-09-12">
    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 the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    519519            <tr>
    520520               <td class="left">Intended status: Standards Track</td>
    521                <td class="right">September 7, 2013</td>
     521               <td class="right">September 12, 2013</td>
    522522            </tr>
    523523            <tr>
    524                <td class="left">Expires: March 11, 2014</td>
     524               <td class="left">Expires: March 16, 2014</td>
    525525               <td class="right"></td>
    526526            </tr>
     
    550550         in progress”.
    551551      </p>
    552       <p>This Internet-Draft will expire on March 11, 2014.</p>
     552      <p>This Internet-Draft will expire on March 16, 2014.</p>
    553553      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    554554      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    13911391      <div id="rfc.iref.c.8"></div>
    13921392      <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a id="cacheable.methods" href="#cacheable.methods">Cacheable Methods</a></h3>
    1393       <p id="rfc.section.4.2.3.p.1">Request methods are considered "<dfn id="cacheable">cacheable</dfn>" if it is possible and useful to answer a current client request with a stored response from a prior request. GET and HEAD
    1394          are defined to be cacheable. In general, safe methods that do not depend on a current or authoritative response are cacheable,
    1395          though the overwhelming majority of caches only support GET and HEAD. HTTP requirements for cache behavior and cacheable responses
    1396          are defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1393      <p id="rfc.section.4.2.3.p.1">Request methods can be defined as "<dfn id="cacheable">cacheable</dfn>" to indicate that responses to them are allowed to be stored for future reuse; for specific requirements see <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. In general, safe methods that do not depend on a current or authoritative response are defined as cacheable; this specification
     1394         defines GET, HEAD and POST as cacheable, although the overwhelming majority of cache implementations only support GET and
     1395         HEAD.
    13971396      </p>
    13981397      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h2>
     
    21942193         protocol.
    21952194      </p>
     2195      <p id="rfc.section.6.1.p.2">Responses with status codes that are defined as cacheable by default (e.g., 200, 203, 206, 300, 301, and 410 in this specification)
     2196         can be reused by a cache with heuristic expiration unless otherwise indicated by the method definition 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.
     2197      </p>
    21962198      <div id="rfc.table.u.9">
    21972199         <table class="tt full left" cellpadding="3" cellspacing="0">
     
    24122414         </table>
    24132415      </div>
    2414       <p id="rfc.section.6.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications. The complete
     2416      <p id="rfc.section.6.1.p.3">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications. The complete
    24152417         list of status codes is maintained by IANA. See <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;8.2</a> for details.
    2416       </p>
    2417       <p id="rfc.section.6.1.p.3">Responses with status codes that are defined as cacheable by default (e.g., 200, 203, 206, 300, 301, and 410 in this specification)
    2418          can be reused by a cache with heuristic expiration unless otherwise indicated by the method definition 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.
    24192418      </p>
    24202419      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
Note: See TracChangeset for help on using the changeset viewer.