Ignore:
Timestamp:
11/11/13 07:34:33 (7 years ago)
Author:
mnot@…
Message:

update p2 html

File:
1 edited

Legend:

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

    r2481 r2483  
    445445  }
    446446  @bottom-center {
    447        content: "Expires May 12, 2014";
     447       content: "Expires May 15, 2014";
    448448  }
    449449  @bottom-right {
     
    485485      <link href="p1-messaging.html" rel="prev">
    486486      <link href="p4-conditional.html" rel="next">
    487       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.607, 2013/10/15 13:23:22, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     487      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.607, 2013/10/15 13:23:22, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
    488488      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    489489      <meta name="dct.creator" content="Fielding, R.">
    490490      <meta name="dct.creator" content="Reschke, J. F.">
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    492       <meta name="dct.issued" scheme="ISO8601" content="2013-11-08">
     492      <meta name="dct.issued" scheme="ISO8601" content="2013-11-11">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    494494      <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.">
     
    518518            <tr>
    519519               <td class="left">Intended status: Standards Track</td>
    520                <td class="right">November 8, 2013</td>
     520               <td class="right">November 11, 2013</td>
    521521            </tr>
    522522            <tr>
    523                <td class="left">Expires: May 12, 2014</td>
     523               <td class="left">Expires: May 15, 2014</td>
    524524               <td class="right"></td>
    525525            </tr>
     
    550550            in progress”.
    551551         </p>
    552          <p>This Internet-Draft will expire on May 12, 2014.</p>
     552         <p>This Internet-Draft will expire on May 15, 2014.</p>
    553553      </div>
    554554      <div id="rfc.copyrightnotice">
     
    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, 206, 300, 301, and 410 in this specification)
    2309                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.
     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
     2310               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.
    23102311            </p>
    23112312            <div id="rfc.table.u.9">
     
    25992600                  200 response header section.
    26002601               </p>
    2601                <p id="rfc.section.6.3.1.p.3">A 200 response is cacheable unless otherwise indicated by the method definition or 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.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2602               <p id="rfc.section.6.3.1.p.3">A 200 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2603                  (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.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    26022604               </p>
    26032605            </div>
     
    26342636               <p id="rfc.section.6.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 5.5</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), which has the advantage of being applicable to responses with any status code.
    26352637               </p>
    2636                <p id="rfc.section.6.3.4.p.3">A 203 response is cacheable unless otherwise indicated by the method definition or 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.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2638               <p id="rfc.section.6.3.4.p.3">A 203 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2639                  (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.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    26372640               </p>
    26382641            </div>
     
    26562659               </p>
    26572660               <p id="rfc.section.6.3.5.p.5">A 204 response is terminated by the first empty line after the header fields because it cannot contain a message body.</p>
    2658                <p id="rfc.section.6.3.5.p.6">A 204 response is cacheable unless otherwise indicated by the method definition or 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.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2661               <p id="rfc.section.6.3.5.p.6">A 204 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2662                  (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.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    26592663               </p>
    26602664            </div>
     
    27272731                  for such automatic selection.
    27282732               </p>
    2729                <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable unless otherwise indicated by the method definition or 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.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2733               <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2734                  (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.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    27302735               </p>
    27312736               <div class="note" id="rfc.section.6.4.1.p.5">
     
    27512756                  </p>
    27522757               </div>
    2753                <p id="rfc.section.6.4.2.p.4">A 301 response is cacheable unless otherwise indicated by the method definition or 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.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2758               <p id="rfc.section.6.4.2.p.4">A 301 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2759                  (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.16"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    27542760               </p>
    27552761            </div>
     
    28552861                  is likely to be permanent.
    28562862               </p>
    2857                <p id="rfc.section.6.5.4.p.2">A 404 response is cacheable unless otherwise indicated by the method definition or 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.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2863               <p id="rfc.section.6.5.4.p.2">A 404 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2864                  (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.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    28582865               </p>
    28592866            </div>
     
    28632870               <p id="rfc.section.6.5.5.p.1">The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method received in the request-line is known by the origin server but not supported by the <a href="#resources" class="smpl">target resource</a>. The origin server <em class="bcp14">MUST</em> generate an <a href="#header.allow" class="smpl">Allow</a> header field in a 405 response containing a list of the target resource's currently supported methods.
    28642871               </p>
    2865                <p id="rfc.section.6.5.5.p.2">A 405 response is cacheable unless otherwise indicated by the method definition or 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.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2872               <p id="rfc.section.6.5.5.p.2">A 405 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2873                  (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.18"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    28662874               </p>
    28672875            </div>
     
    29082916                  any length of time — that is left to the discretion of the server owner.
    29092917               </p>
    2910                <p id="rfc.section.6.5.9.p.3">A 410 response is cacheable unless otherwise indicated by the method definition or 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.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2918               <p id="rfc.section.6.5.9.p.3">A 410 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2919                  (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.19"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    29112920               </p>
    29122921            </div>
     
    29352944                  attempting to exploit potential security holes.
    29362945               </p>
    2937                <p id="rfc.section.6.5.12.p.2">A 414 response is cacheable unless otherwise indicated by the method definition or 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.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2946               <p id="rfc.section.6.5.12.p.2">A 414 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     2947                  (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.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    29382948               </p>
    29392949            </div>
     
    29872997                  response when the server does not recognize the request method and is not capable of supporting it for any resource.
    29882998               </p>
    2989                <p id="rfc.section.6.6.2.p.2">A 501 response is cacheable unless otherwise indicated by the method definition or 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.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     2999               <p id="rfc.section.6.6.2.p.2">A 501 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls
     3000                  (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.21"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    29903001               </p>
    29913002            </div>
Note: See TracChangeset for help on using the changeset viewer.