![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 262 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- Jun 12, 2008, 2:57:07 AM (12 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p2-semantics.html (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r261 r262 419 419 </tr> 420 420 <tr> 421 <td class="header left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved) 422 </td> 423 <td class="header right">J. Mogul</td> 424 </tr> 425 <tr> 421 426 <td class="header left">Intended status: Standards Track</td> 422 <td class="header right"> J. Mogul</td>427 <td class="header right">HP</td> 423 428 </tr> 424 429 <tr> 425 430 <td class="header left">Expires: December 2008</td> 426 <td class="header right">HP</td>427 </tr>428 <tr>429 <td class="header left"></td>430 431 <td class="header right">H. Frystyk</td> 431 432 </tr> … … 476 477 <tr> 477 478 <td class="header left"></td> 478 <td class="header right">June 6, 2008</td>479 <td class="header right">June 12, 2008</td> 479 480 </tr> 480 481 </table> … … 520 521 <li class="tocline0">3. <a href="#method">Method</a></li> 521 522 <li class="tocline0">4. <a href="#request.header.fields">Request Header Fields</a></li> 522 <li class="tocline0">5. <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 523 <li class="tocline0">5. <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc"> 524 <li class="tocline1">5.1 <a href="#status.code.registry">Status Code Registry</a></li> 525 </ul> 526 </li> 523 527 <li class="tocline0">6. <a href="#response.header.fields">Response Header Fields</a></li> 524 528 <li class="tocline0">7. <a href="#entity">Entity</a></li> … … 809 813 which will explain the unusual status. 810 814 </p> 815 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2> 816 <p id="rfc.section.5.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response.</p> 817 <p id="rfc.section.5.1.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). Any document registering new status codes should be traceable through statuses of either 'Obsoletes' or 'Updates' to this 818 document. 819 </p> 820 <p id="rfc.section.5.1.p.3">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 821 </p> 811 822 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1> 812 823 <p id="rfc.section.6.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the … … 1579 1590 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1580 1591 <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2> 1581 <p id="rfc.section.11.1.p.1">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>> should be updated with the registrations below (see <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>, <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a>). 1592 <p id="rfc.section.11.1.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 5.1</a> of this document. 1593 </p> 1594 <p id="rfc.section.11.1.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>> should be updated with the registrations below: 1582 1595 </p> 1583 1596 <div id="rfc.table.u.1"> … … 2012 2025 <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References 2013 2026 </h2> 2014 <table summary="Informative References"> 2027 <table summary="Informative References"> 2015 2028 <tr> 2016 2029 <td class="reference"><b id="Luo1998">[Luo1998]</b></td> … … 2046 2059 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 2047 2060 <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. 2061 </td> 2062 </tr> 2063 <tr> 2064 <td class="reference"><b id="RFC5226">[RFC5226]</b></td> 2065 <td class="top"><a title="IBM">Narten, T.</a> and <a title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP 26, RFC 5226, May 2008. 2048 2066 </td> 2049 2067 </tr> … … 2094 2112 </p> 2095 2113 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 2096 <p id="rfc.section.A.2.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section 8.5</a>) 2097 </p> 2098 <p id="rfc.section.A.2.p.2">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 2114 <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, 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.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 5.1</a>) 2115 </p> 2116 <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section 8.5</a>) 2117 </p> 2118 <p id="rfc.section.A.2.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 2099 2119 user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">9.3.8</a>) 2100 2120 </p> 2101 <p id="rfc.section.A.2.p. 3">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource2121 <p id="rfc.section.A.2.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource 2102 2122 must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient 2103 2123 was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 9.3.6</a>) 2104 2124 </p> 2105 <p id="rfc.section.A.2.p. 4">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement2125 <p id="rfc.section.A.2.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement 2106 2126 on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 10.1</a>) 2107 2127 </p> 2108 <p id="rfc.section.A.2.p. 5">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications2128 <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 2109 2129 as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 10.4</a>) 2110 2130 </p> 2111 <p id="rfc.section.A.2.p. 6">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly2131 <p id="rfc.section.A.2.p.7">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 2112 2132 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 10.8</a>) 2113 2133 </p> … … 2164 2184 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24</a>>: "Requiring Allow in 405 responses" 2165 2185 </li> 2186 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59</a>>: "Status Code Registry" 2187 </li> 2166 2188 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61</a>>: "Redirection vs. Location" 2167 2189 </li> … … 2180 2202 <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li> 2181 2203 </ul> 2182 <p id="rfc.section.B.4.p.3">Ongoing work on IANA HTTP Status Code Registration (<<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59</a>>): 2183 </p> 2184 <ul> 2185 <li>Reference RFC 2817, and update the HTTP status code registrations.</li> 2186 </ul> 2187 <p id="rfc.section.B.4.p.4">Ongoing work on ABNF conversion (<<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 2204 <p id="rfc.section.B.4.p.3">Ongoing work on ABNF conversion (<<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 2188 2205 </p> 2189 2206 <ul> … … 2431 2448 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li> 2432 2449 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li> 2433 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">11.1</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a> <ul class="ind">2434 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.RFC2817.1">11.1</a> </li>2450 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">11.1</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A.2</a><ul class="ind"> 2451 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.RFC2817.1">11.1</a>, <a class="iref" href="#rfc.xref.RFC2817.2">A.2</a></li> 2435 2452 </ul> 2436 2453 </li> … … 2440 2457 </li> 2441 2458 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">11.2</a>, <a class="iref" href="#RFC3864"><b>14.2</b></a></li> 2459 <li class="indline1"><em>RFC5226</em> <a class="iref" href="#rfc.xref.RFC5226.1">5.1</a>, <a class="iref" href="#RFC5226"><b>14.2</b></a><ul class="ind"> 2460 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.RFC5226.1">5.1</a></li> 2461 </ul> 2462 </li> 2442 2463 </ul> 2443 2464 </li>
Note: See TracChangeset
for help on using the changeset viewer.
