Changeset 1101 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 08/01/11 14:27:21 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1099 r1101 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2011-01-0 1">405 <meta name="dct.issued" scheme="ISO8601" content="2011-01-08"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: July 5, 2011</td>436 <td class="left">Expires: July 12, 2011</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">January 1, 2011</td>489 <td class="right">January 8, 2011</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on July 5, 2011.</p>516 <p>This Internet-Draft will expire on July 12, 2011.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 848 848 </p> 849 849 <p id="rfc.section.4.p.3">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase 850 values, are presented below. The reason phrases listed here are only recommendations --they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol.850 values, are presented below. The reason phrases listed here are only recommendations — they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol. 851 851 </p> 852 852 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = … … 1152 1152 Host: server.example.com:80 1153 1153 1154 </pre><p id="rfc.section.7.9.p.4">Other HTTP mechanisms can be used normally with the CONNECT method --except end-to-end protocol Upgrade requests, since the1154 </pre><p id="rfc.section.7.9.p.4">Other HTTP mechanisms can be used normally with the CONNECT method — except end-to-end protocol Upgrade requests, since the 1155 1155 tunnel must be established first. 1156 1156 </p> … … 1492 1492 is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's 1493 1493 site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time 1494 --that is left to the discretion of the server owner.1494 — that is left to the discretion of the server owner. 1495 1495 </p> 1496 1496 <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses. … … 1617 1617 <div id="rfc.figure.u.16"></div><pre class="text"> Allow: GET, HEAD, PUT 1618 1618 </pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p> 1619 <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field --it does not need to understand all the methods specified in order to handle them according1619 <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according 1620 1620 to the generic message handling rules. 1621 1621 </p> … … 1864 1864 </div> 1865 1865 <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2> 1866 <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> --is now defined by <a href="#status.code.registry" title="Status Code Registry">Section 4.1</a> of this document.1866 <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes — previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section 4.1</a> of this document. 1867 1867 </p> 1868 1868 <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below:
Note: See TracChangeset
for help on using the changeset viewer.