![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2301 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 01/07/13 08:47:55 (8 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p2-semantics.html (modified) (103 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2294 r2301 440 440 } 441 441 @top-right { 442 content: "Ju ne2013";442 content: "July 2013"; 443 443 } 444 444 @top-center { … … 449 449 } 450 450 @bottom-center { 451 content: "Expires December 18, 2013";451 content: "Expires January 2, 2014"; 452 452 } 453 453 @bottom-right { … … 489 489 <link href="p1-messaging.html" rel="prev"> 490 490 <link href="p4-conditional.html" rel="next"> 491 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.59 7, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">491 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 492 492 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 493 493 <meta name="dct.creator" content="Fielding, R."> 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-0 6-16">496 <meta name="dct.issued" scheme="ISO8601" content="2013-07-01"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <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."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">Ju ne 16, 2013</td>524 <td class="right">July 1, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: December 18, 2013</td>527 <td class="left">Expires: January 2, 2014</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on December 18, 2013.</p>555 <p>This Internet-Draft will expire on January 2, 2014.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 896 896 <a href="#media.type" class="smpl">subtype</a> = <a href="#imported.abnf" class="smpl">token</a> 897 897 </pre><div id="rule.parameter"> 898 <p id="rfc.section.3.1.1.1.p.3"> 898 <p id="rfc.section.3.1.1.1.p.3"> The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs. 899 899 </p> 900 900 </div> … … 915 915 </pre><p id="rfc.section.3.1.1.1.p.8">Internet media types ought to be registered with IANA according to the procedures defined in <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>. 916 916 </p> 917 <div class="note" id="rfc.section.3.1.1.1.p.9"> 918 <p> 917 <div class="note" id="rfc.section.3.1.1.1.p.9"> 918 <p><b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace) 919 919 around the "=" character. 920 920 </p> … … 1027 1027 other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> header fields. 1028 1028 </p> 1029 <p id="rfc.section.3.1.3.1.p.2"> 1029 <p id="rfc.section.3.1.3.1.p.2"><a href="#header.accept-language" class="smpl">Accept-Language</a> uses the looser language-range production defined in <a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section 5.3.5</a>, whereas <a href="#header.content-language" class="smpl">Content-Language</a> uses the stricter language-tag production defined below. 1030 1030 </p> 1031 1031 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.12"></span> <a href="#language.tags" class="smpl">language-tag</a> = <Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>> … … 1688 1688 <h4 id="rfc.section.5.1.1.1"><a href="#rfc.section.5.1.1.1">5.1.1.1</a> <a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4> 1689 1689 <p id="rfc.section.5.1.1.1.p.1">The only expectation defined by this specification is:</p> 1690 <p id="rfc.section.5.1.1.1.p.2"> <dfn>100-continue</dfn>1690 <p id="rfc.section.5.1.1.1.p.2"><dfn>100-continue</dfn> 1691 1691 </p> 1692 1692 <ul class="empty"> … … 1862 1862 since it acts as a separator between the two parameter sets. 1863 1863 </p> 1864 <div class="note" id="rfc.section.5.3.2.p.5"> 1865 <p> 1864 <div class="note" id="rfc.section.5.3.2.p.5"> 1865 <p><b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice. 1866 1866 Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to 1867 1867 be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters … … 1871 1871 <p id="rfc.section.5.3.2.p.6">The example</p> 1872 1872 <div id="rfc.figure.u.24"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 1873 </pre><p id="rfc.section.5.3.2.p.8"> 1873 </pre><p id="rfc.section.5.3.2.p.8"><em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in 1874 1874 quality". 1875 1875 </p> … … 1937 1937 </table> 1938 1938 </div> 1939 <p id="rfc.section.5.3.2.p.19"> 1939 <p id="rfc.section.5.3.2.p.19"><b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent 1940 1940 is a closed system that cannot interact with other rendering agents, this default set ought to be configurable by the user. 1941 1941 </p> … … 1996 1996 response have a content-coding that is listed as acceptable, the origin server <em class="bcp14">SHOULD</em> send a response without any content-coding. 1997 1997 </p> 1998 <div class="note" id="rfc.section.5.3.4.p.9"> 1999 <p> 1998 <div class="note" id="rfc.section.5.3.4.p.9"> 1999 <p><b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues might 2000 2000 not work and are not permitted with x-gzip or x-compress. 2001 2001 </p> … … 2034 2034 preference. A user agent that does not provide such control to the user <em class="bcp14">MUST NOT</em> send an Accept-Language header field. 2035 2035 </p> 2036 <div class="note" id="rfc.section.5.3.5.p.11"> 2037 <p> 2036 <div class="note" id="rfc.section.5.3.5.p.11"> 2037 <p><b>Note:</b> User agents ought to provide guidance to users when setting a preference, since users are rarely familiar with the details 2038 2038 of language matching as described above. For example, users might assume that on selecting "en-gb", they will be served any 2039 2039 kind of English document if British English is not available. A user agent might suggest, in such a case, to add "en" to the … … 2177 2177 </p> 2178 2178 <ul> 2179 <li> 2180 </li> 2181 <li> 2182 </li> 2183 <li> 2184 </li> 2185 <li> 2186 </li> 2187 <li> 2179 <li><a href="#status.1xx" class="smpl">1xx (Informational)</a>: The request was received, continuing process 2180 </li> 2181 <li><a href="#status.2xx" class="smpl">2xx (Successful)</a>: The request was successfully received, understood, and accepted 2182 </li> 2183 <li><a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request 2184 </li> 2185 <li><a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled 2186 </li> 2187 <li><a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request 2188 2188 </li> 2189 2189 </ul> … … 2564 2564 </li> 2565 2565 </ol> 2566 <div class="note" id="rfc.section.6.4.p.3"> 2567 <p> 2566 <div class="note" id="rfc.section.6.4.p.3"> 2567 <p><b>Note:</b> In HTTP/1.0, the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). Early user agents split on whether the method applied to the redirect target would be the same as the original request 2568 2568 or would be rewritten as GET. Although HTTP originally defined the former semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> (to match its original implementation at CERN), and defined <a href="#status.303" class="smpl">303 (See Other)</a> to match the latter semantics, prevailing practice gradually converged on the latter semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> as well. The first revision of HTTP/1.1 added <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> to indicate the former semantics without being impacted by divergent practice. Over 10 years later, most user agents still 2569 2569 do method rewriting for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>; therefore, this specification makes that behavior conformant when the original request is POST. … … 2572 2572 <p id="rfc.section.6.4.p.4">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops). 2573 2573 </p> 2574 <div class="note" id="rfc.section.6.4.p.5"> 2575 <p> 2574 <div class="note" id="rfc.section.6.4.p.5"> 2575 <p><b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation. 2576 2576 </p> 2577 2577 </div> … … 2591 2591 <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.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). 2592 2592 </p> 2593 <div class="note" id="rfc.section.6.4.1.p.5"> 2594 <p> 2593 <div class="note" id="rfc.section.6.4.1.p.5"> 2594 <p><b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it 2595 2595 would be usable for 200, 300, and 406 responses and be transferred in responses to the HEAD method. However, lack of deployment 2596 2596 and disagreement over syntax led to both URI and Alternates (a subsequent proposal) being dropped from this specification. … … 2607 2607 with a hyperlink to the new URI(s). 2608 2608 </p> 2609 <div class="note" id="rfc.section.6.4.2.p.3"> 2610 <p> 2609 <div class="note" id="rfc.section.6.4.2.p.3"> 2610 <p><b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead. 2611 2611 </p> 2612 2612 </div> … … 2621 2621 with a hyperlink to the different URI(s). 2622 2622 </p> 2623 <div class="note" id="rfc.section.6.4.3.p.3"> 2624 <p> 2623 <div class="note" id="rfc.section.6.4.3.p.3"> 2624 <p><b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead. 2625 2625 </p> 2626 2626 </div> … … 2659 2659 with a hyperlink to the different URI(s). 2660 2660 </p> 2661 <div class="note" id="rfc.section.6.4.7.p.3"> 2662 <p> 2661 <div class="note" id="rfc.section.6.4.7.p.3"> 2662 <p><b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow changing the request method from POST to GET. This specification defines no equivalent counterpart 2663 2663 for <a href="#status.301" class="smpl">301 (Moved 2664 2664 Permanently)</a> (<a href="#status-308" id="rfc.xref.status-308.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[status-308]</cite></a>, however, defines the status code 308 (Permanent Redirect) for this purpose). … … 2687 2687 <p id="rfc.section.6.5.3.p.2">If authentication credentials were provided in the request, the server considers them insufficient to grant access. The client <em class="bcp14">SHOULD NOT</em> repeat the request with the same credentials. The client <em class="bcp14">MAY</em> repeat the request with new or different credentials. However, a request might be forbidden for reasons unrelated to the credentials. 2688 2688 </p> 2689 <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a> 2689 <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a> <em class="bcp14">MAY</em> instead respond with a status code of <a href="#status.404" class="smpl">404 (Not Found)</a>. 2690 2690 </p> 2691 2691 <div id="rfc.iref.76"></div> … … 2811 2811 which will likely be alleviated after some delay. The server <em class="bcp14">MAY</em> send a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 7.1.3</a>) to suggest an appropriate amount of time for the client to wait before retrying the request. 2812 2812 </p> 2813 <div class="note" id="rfc.section.6.6.4.p.2"> 2814 <p> 2813 <div class="note" id="rfc.section.6.6.4.p.2"> 2814 <p><b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might 2815 2815 simply refuse the connection. 2816 2816 </p> … … 2902 2902 </p> 2903 2903 <div id="preferred.date.format"> 2904 <p id="rfc.section.7.1.1.1.p.7"> 2904 <p id="rfc.section.7.1.1.1.p.7"> Preferred format:</p> 2905 2905 </div> 2906 2906 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span> <a href="#preferred.date.format" class="smpl">IMF-fixdate</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> … … 2943 2943 <a href="#preferred.date.format" class="smpl">second</a> = 2<a href="#imported.abnf" class="smpl">DIGIT</a> 2944 2944 </pre><div id="obsolete.date.formats"> 2945 <p id="rfc.section.7.1.1.1.p.9"> 2945 <p id="rfc.section.7.1.1.1.p.9"> Obsolete formats:</p> 2946 2946 </div> 2947 2947 <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.52"></span> <a href="#obsolete.date.formats" class="smpl">obs-date</a> = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a> … … 2969 2969 date and time specifications defined by the Internet Message Format. 2970 2970 </p> 2971 <div class="note" id="rfc.section.7.1.1.1.p.16"> 2972 <p> 2971 <div class="note" id="rfc.section.7.1.1.1.p.16"> 2972 <p><b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are 2973 2973 not required to use these formats for user presentation, request logging, etc. 2974 2974 </p> … … 3023 3023 header field in a <a href="#status.201" class="smpl">201 (Created)</a> response is supposed to provide a URI that is specific to the created resource. 3024 3024 </p> 3025 <div class="note" id="rfc.section.7.1.2.p.9"> 3026 <p> 3025 <div class="note" id="rfc.section.7.1.2.p.9"> 3026 <p><b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate 3027 3027 or define such processing, but does allow it for the sake of robustness. 3028 3028 </p> 3029 3029 </div> 3030 <div class="note" id="rfc.section.7.1.2.p.10"> 3031 <p> 3030 <div class="note" id="rfc.section.7.1.2.p.10"> 3031 <p><b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section 3.1.4.2</a>) differs from Location in that the Content-Location refers to the most specific resource corresponding to the enclosed representation. 3032 3032 It is therefore possible for a response to contain both the Location and Content-Location header fields. 3033 3033 </p> … … 3041 3041 <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.57"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 3042 3042 </pre><div id="rule.delta-seconds"> 3043 <p id="rfc.section.7.1.3.p.4"> 3043 <p id="rfc.section.7.1.3.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p> 3044 3044 </div> 3045 3045 <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.58"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> … … 3232 3232 response semantics (<a href="#Part5" id="rfc.xref.Part5.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), it ought to document this too. 3233 3233 </p> 3234 <div class="note" id="rfc.section.8.1.2.p.4"> 3235 <p> 3234 <div class="note" id="rfc.section.8.1.2.p.4"> 3235 <p><b>Note:</b> Avoid defining a method name that starts with "M-", since that prefix might be misinterpreted as having the semantics assigned 3236 3236 to it by <a href="#RFC2774" id="rfc.xref.RFC2774.1"><cite title="An HTTP Extension Framework">[RFC2774]</cite></a>. 3237 3237 </p> … … 3255 3255 <td class="left">no</td> 3256 3256 <td class="left">no</td> 3257 <td class="left"> 3257 <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section 4.3.6</a> 3258 3258 </td> 3259 3259 </tr> … … 3262 3262 <td class="left">no</td> 3263 3263 <td class="left">yes</td> 3264 <td class="left"> 3264 <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section 4.3.5</a> 3265 3265 </td> 3266 3266 </tr> … … 3269 3269 <td class="left">yes</td> 3270 3270 <td class="left">yes</td> 3271 <td class="left"> 3271 <td class="left"><a href="#GET" id="rfc.xref.GET.4" title="GET">Section 4.3.1</a> 3272 3272 </td> 3273 3273 </tr> … … 3276 3276 <td class="left">yes</td> 3277 3277 <td class="left">yes</td> 3278 <td class="left"> 3278 <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section 4.3.2</a> 3279 3279 </td> 3280 3280 </tr> … … 3283 3283 <td class="left">yes</td> 3284 3284 <td class="left">yes</td> 3285 <td class="left"> 3285 <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section 4.3.7</a> 3286 3286 </td> 3287 3287 </tr> … … 3290 3290 <td class="left">no</td> 3291 3291 <td class="left">no</td> 3292 <td class="left"> 3292 <td class="left"><a href="#POST" id="rfc.xref.POST.3" title="POST">Section 4.3.3</a> 3293 3293 </td> 3294 3294 </tr> … … 3297 3297 <td class="left">no</td> 3298 3298 <td class="left">yes</td> 3299 <td class="left"> 3299 <td class="left"><a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section 4.3.4</a> 3300 3300 </td> 3301 3301 </tr> … … 3304 3304 <td class="left">yes</td> 3305 3305 <td class="left">yes</td> 3306 <td class="left"> 3306 <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section 4.3.8</a> 3307 3307 </td> 3308 3308 </tr> … … 3367 3367 <td class="left">100</td> 3368 3368 <td class="left">Continue</td> 3369 <td class="left"> 3369 <td class="left"><a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section 6.2.1</a> 3370 3370 </td> 3371 3371 </tr> … … 3373 3373 <td class="left">101</td> 3374 3374 <td class="left">Switching Protocols</td> 3375 <td class="left"> 3375 <td class="left"><a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section 6.2.2</a> 3376 3376 </td> 3377 3377 </tr> … … 3379 3379 <td class="left">200</td> 3380 3380 <td class="left">OK</td> 3381 <td class="left"> 3381 <td class="left"><a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section 6.3.1</a> 3382 3382 </td> 3383 3383 </tr> … … 3385 3385 <td class="left">201</td> 3386 3386 <td class="left">Created</td> 3387 <td class="left"> 3387 <td class="left"><a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section 6.3.2</a> 3388 3388 </td> 3389 3389 </tr> … … 3391 3391 <td class="left">202</td> 3392 3392 <td class="left">Accepted</td> 3393 <td class="left"> 3393 <td class="left"><a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section 6.3.3</a> 3394 3394 </td> 3395 3395 </tr> … … 3397 3397 <td class="left">203</td> 3398 3398 <td class="left">Non-Authoritative Information</td> 3399 <td class="left"> 3399 <td class="left"><a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section 6.3.4</a> 3400 3400 </td> 3401 3401 </tr> … … 3403 3403 <td class="left">204</td> 3404 3404 <td class="left">No Content</td> 3405 <td class="left"> 3405 <td class="left"><a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section 6.3.5</a> 3406 3406 </td> 3407 3407 </tr> … … 3409 3409 <td class="left">205</td> 3410 3410 <td class="left">Reset Content</td> 3411 <td class="left"> 3411 <td class="left"><a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section 6.3.6</a> 3412 3412 </td> 3413 3413 </tr> … … 3415 3415 <td class="left">300</td> 3416 3416 <td class="left">Multiple Choices</td> 3417 <td class="left"> 3417 <td class="left"><a href="#status.300" id="rfc.xref.status.300.3" title="300 Multiple Choices">Section 6.4.1</a> 3418 3418 </td> 3419 3419 </tr> … … 3421 3421 <td class="left">301</td> 3422 3422 <td class="left">Moved Permanently</td> 3423 <td class="left"> 3423 <td class="left"><a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section 6.4.2</a> 3424 3424 </td> 3425 3425 </tr> … … 3427 3427 <td class="left">302</td> 3428 3428 <td class="left">Found</td> 3429 <td class="left"> 3429 <td class="left"><a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section 6.4.3</a> 3430 3430 </td> 3431 3431 </tr> … … 3433 3433 <td class="left">303</td> 3434 3434 <td class="left">See Other</td> 3435 <td class="left"> 3435 <td class="left"><a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section 6.4.4</a> 3436 3436 </td> 3437 3437 </tr> … … 3439 3439 <td class="left">305</td> 3440 3440 <td class="left">Use Proxy</td> 3441 <td class="left"> 3441 <td class="left"><a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section 6.4.5</a> 3442 3442 </td> 3443 3443 </tr> … … 3445 3445 <td class="left">306</td> 3446 3446 <td class="left">(Unused)</td> 3447 <td class="left"> 3447 <td class="left"><a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section 6.4.6</a> 3448 3448 </td> 3449 3449 </tr> … … 3451 3451 <td class="left">307</td> 3452 3452 <td class="left">Temporary Redirect</td> 3453 <td class="left"> 3453 <td class="left"><a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section 6.4.7</a> 3454 3454 </td> 3455 3455 </tr> … … 3457 3457 <td class="left">400</td> 3458 3458 <td class="left">Bad Request</td> 3459 <td class="left"> 3459 <td class="left"><a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section 6.5.1</a> 3460 3460 </td> 3461 3461 </tr> … … 3463 3463 <td class="left">402</td> 3464 3464 <td class="left">Payment Required</td> 3465 <td class="left"> 3465 <td class="left"><a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section 6.5.2</a> 3466 3466 </td> 3467 3467 </tr> … … 3469 3469 <td class="left">403</td> 3470 3470 <td class="left">Forbidden</td> 3471 <td class="left"> 3471 <td class="left"><a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section 6.5.3</a> 3472 3472 </td> 3473 3473 </tr> … … 3475 3475 <td class="left">404</td> 3476 3476 <td class="left">Not Found</td> 3477 <td class="left"> 3477 <td class="left"><a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section 6.5.4</a> 3478 3478 </td> 3479 3479 </tr> … … 3481 3481 <td class="left">405</td> 3482 3482 <td class="left">Method Not Allowed</td> 3483 <td class="left"> 3483 <td class="left"><a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section 6.5.5</a> 3484 3484 </td> 3485 3485 </tr> … … 3487 3487 <td class="left">406</td> 3488 3488 <td class="left">Not Acceptable</td> 3489 <td class="left"> 3489 <td class="left"><a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section 6.5.6</a> 3490 3490 </td> 3491 3491 </tr> … … 3493 3493 <td class="left">408</td> 3494 3494 <td class="left">Request Timeout</td> 3495 <td class="left"> 3495 <td class="left"><a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section 6.5.7</a> 3496 3496 </td> 3497 3497 </tr> … … 3499 3499 <td class="left">409</td> 3500 3500 <td class="left">Conflict</td> 3501 <td class="left"> 3501 <td class="left"><a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section 6.5.8</a> 3502 3502 </td> 3503 3503 </tr> … … 3505 3505 <td class="left">410</td> 3506 3506 <td class="left">Gone</td> 3507 <td class="left"> 3507 <td class="left"><a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section 6.5.9</a> 3508 3508 </td> 3509 3509 </tr> … … 3511 3511 <td class="left">411</td> 3512 3512 <td class="left">Length Required</td> 3513 <td class="left"> 3513 <td class="left"><a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section 6.5.10</a> 3514 3514 </td> 3515 3515 </tr> … … 3517 3517 <td class="left">413</td> 3518 3518 <td class="left">Payload Too Large</td> 3519 <td class="left"> 3519 <td class="left"><a href="#status.413" id="rfc.xref.status.413.2" title="413 Payload Too Large">Section 6.5.11</a> 3520 3520 </td> 3521 3521 </tr> … … 3523 3523 <td class="left">414</td> 3524 3524 <td class="left">URI Too Long</td> 3525 <td class="left"> 3525 <td class="left"><a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section 6.5.12</a> 3526 3526 </td> 3527 3527 </tr> … … 3529 3529 <td class="left">415</td> 3530 3530 <td class="left">Unsupported Media Type</td> 3531 <td class="left"> 3531 <td class="left"><a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section 6.5.13</a> 3532 3532 </td> 3533 3533 </tr> … … 3535 3535 <td class="left">417</td> 3536 3536 <td class="left">Expectation Failed</td> 3537 <td class="left"> 3537 <td class="left"><a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section 6.5.14</a> 3538 3538 </td> 3539 3539 </tr> … … 3541 3541 <td class="left">426</td> 3542 3542 <td class="left">Upgrade Required</td> 3543 <td class="left"> 3543 <td class="left"><a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section 6.5.15</a> 3544 3544 </td> 3545 3545 </tr> … … 3547 3547 <td class="left">500</td> 3548 3548 <td class="left">Internal Server Error</td> 3549 <td class="left"> 3549 <td class="left"><a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section 6.6.1</a> 3550 3550 </td> 3551 3551 </tr> … … 3553 3553 <td class="left">501</td> 3554 3554 <td class="left">Not Implemented</td> 3555 <td class="left"> 3555 <td class="left"><a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section 6.6.2</a> 3556 3556 </td> 3557 3557 </tr> … … 3559 3559 <td class="left">502</td> 3560 3560 <td class="left">Bad Gateway</td> 3561 <td class="left"> 3561 <td class="left"><a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section 6.6.3</a> 3562 3562 </td> 3563 3563 </tr> … … 3565 3565 <td class="left">503</td> 3566 3566 <td class="left">Service Unavailable</td> 3567 <td class="left"> 3567 <td class="left"><a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section 6.6.4</a> 3568 3568 </td> 3569 3569 </tr> … … 3571 3571 <td class="left">504</td> 3572 3572 <td class="left">Gateway Timeout</td> 3573 <td class="left"> 3573 <td class="left"><a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section 6.6.5</a> 3574 3574 </td> 3575 3575 </tr> … … 3577 3577 <td class="left">505</td> 3578 3578 <td class="left">HTTP Version Not Supported</td> 3579 <td class="left"> 3579 <td class="left"><a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section 6.6.6</a> 3580 3580 </td> 3581 3581 </tr> … … 3680 3680 <td class="left">http</td> 3681 3681 <td class="left">standard</td> 3682 <td class="left"> 3682 <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section 5.3.2</a> 3683 3683 </td> 3684 3684 </tr> … … 3687 3687 <td class="left">http</td> 3688 3688 <td class="left">standard</td> 3689 <td class="left"> 3689 <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section 5.3.3</a> 3690 3690 </td> 3691 3691 </tr> … … 3694 3694 <td class="left">http</td> 3695 3695 <td class="left">standard</td> 3696 <td class="left"> 3696 <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section 5.3.4</a> 3697 3697 </td> 3698 3698 </tr> … … 3701 3701 <td class="left">http</td> 3702 3702 <td class="left">standard</td> 3703 <td class="left"> 3703 <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section 5.3.5</a> 3704 3704 </td> 3705 3705 </tr> … … 3708 3708 <td class="left">http</td> 3709 3709 <td class="left">standard</td> 3710 <td class="left"> 3710 <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section 7.4.1</a> 3711 3711 </td> 3712 3712 </tr> … … 3715 3715 <td class="left">http</td> 3716 3716 <td class="left">standard</td> 3717 <td class="left"> 3717 <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section 3.1.2.2</a> 3718 3718 </td> 3719 3719 </tr> … … 3722 3722 <td class="left">http</td> 3723 3723 <td class="left">standard</td> 3724 <td class="left"> 3724 <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section 3.1.3.2</a> 3725 3725 </td> 3726 3726 </tr> … … 3729 3729 <td class="left">http</td> 3730 3730 <td class="left">standard</td> 3731 <td class="left"> 3731 <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section 3.1.4.2</a> 3732 3732 </td> 3733 3733 </tr> … … 3736 3736 <td class="left">http</td> 3737 3737 <td class="left">standard</td> 3738 <td class="left"> 3738 <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section 3.1.1.5</a> 3739 3739 </td> 3740 3740 </tr> … … 3743 3743 <td class="left">http</td> 3744 3744 <td class="left">standard</td> 3745 <td class="left"> 3745 <td class="left"><a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section 7.1.1.2</a> 3746 3746 </td> 3747 3747 </tr> … … 3750 3750 <td class="left">http</td> 3751 3751 <td class="left">standard</td> 3752 <td class="left"> 3752 <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section 5.1.1</a> 3753 3753 </td> 3754 3754 </tr> … … 3757 3757 <td class="left">http</td> 3758 3758 <td class="left">standard</td> 3759 <td class="left"> 3759 <td class="left"><a href="#header.from" id="rfc.xref.header.from.2" title="From">Section 5.5.1</a> 3760 3760 </td> 3761 3761 </tr> … … 3764 3764 <td class="left">http</td> 3765 3765 <td class="left">standard</td> 3766 <td class="left"> 3766 <td class="left"><a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 7.1.2</a> 3767 3767 </td> 3768 3768 </tr> … … 3771 3771 <td class="left">http</td> 3772 3772 <td class="left">standard</td> 3773 <td class="left"> 3773 <td class="left"><a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix A.1</a> 3774 3774 </td> 3775 3775 </tr> … … 3778 3778 <td class="left">http</td> 3779 3779 <td class="left">standard</td> 3780 <td class="left"> 3780 <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section 5.1.2</a> 3781 3781 </td> 3782 3782 </tr> … … 3785 3785 <td class="left">http</td> 3786 3786 <td class="left">standard</td> 3787 <td class="left"> 3787 <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section 5.5.2</a> 3788 3788 </td> 3789 3789 </tr> … … 3792 3792 <td class="left">http</td> 3793 3793 <td class="left">standard</td> 3794 <td class="left"> 3794 <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section 7.1.3</a> 3795 3795 </td> 3796 3796 </tr> … … 3799 3799 <td class="left">http</td> 3800 3800 <td class="left">standard</td> 3801 <td class="left"> 3801 <td class="left"><a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section 7.4.2</a> 3802 3802 </td> 3803 3803 </tr> … … 3806 3806 <td class="left">http</td> 3807 3807 <td class="left">standard</td> 3808 <td class="left"> 3808 <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section 5.5.3</a> 3809 3809 </td> 3810 3810 </tr> … … 3813 3813 <td class="left">http</td> 3814 3814 <td class="left">standard</td> 3815 <td class="left"> 3815 <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section 7.1.4</a> 3816 3816 </td> 3817 3817 </tr> … … 3851 3851 <td class="left">compress</td> 3852 3852 <td class="left">UNIX "compress" data format <a href="#Welch" id="rfc.xref.Welch.1"><cite title="A Technique for High Performance Data Compression">[Welch]</cite></a></td> 3853 <td class="left"> 3853 <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3854 3854 </td> 3855 3855 </tr> … … 3858 3858 <td class="left">"deflate" compressed data (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 3859 3859 </td> 3860 <td class="left"> 3860 <td class="left"><a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3861 3861 </td> 3862 3862 </tr> … … 3864 3864 <td class="left">gzip</td> 3865 3865 <td class="left">GZIP file format <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 3866 <td class="left"> 3866 <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3867 3867 </td> 3868 3868 </tr> … … 3871 3871 <td class="left">Reserved (synonym for "no encoding" in <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>) 3872 3872 </td> 3873 <td class="left"> 3873 <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section 5.3.4</a> 3874 3874 </td> 3875 3875 </tr> … … 3877 3877 <td class="left">x-compress</td> 3878 3878 <td class="left">Deprecated (alias for compress)</td> 3879 <td class="left"> 3879 <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3880 3880 </td> 3881 3881 </tr> … … 3883 3883 <td class="left">x-gzip</td> 3884 3884 <td class="left">Deprecated (alias for gzip)</td> 3885 <td class="left"> 3885 <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> 3886 3886 </td> 3887 3887 </tr> … … 3979 3979 <tr> 3980 3980 <td class="reference"><b id="Part1">[Part1]</b></td> 3981 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), Ju ne 2013.3981 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), July 2013. 3982 3982 </td> 3983 3983 </tr> 3984 3984 <tr> 3985 3985 <td class="reference"><b id="Part4">[Part4]</b></td> 3986 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), Ju ne 2013.3986 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), July 2013. 3987 3987 </td> 3988 3988 </tr> 3989 3989 <tr> 3990 3990 <td class="reference"><b id="Part5">[Part5]</b></td> 3991 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), Ju ne 2013.3991 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), July 2013. 3992 3992 </td> 3993 3993 </tr> 3994 3994 <tr> 3995 3995 <td class="reference"><b id="Part6">[Part6]</b></td> 3996 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), Ju ne 2013.3996 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), July 2013. 3997 3997 </td> 3998 3998 </tr> 3999 3999 <tr> 4000 4000 <td class="reference"><b id="Part7">[Part7]</b></td> 4001 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), Ju ne 2013.4001 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), July 2013. 4002 4002 </td> 4003 4003 </tr> … … 4294 4294 information present): 204, 404, 405, 414, 501. 4295 4295 </p> 4296 <p id="rfc.section.B.p.24"> 4296 <p id="rfc.section.B.p.24"><a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. Requirements relating 4297 4297 to the content of Allow have been relaxed; correspondingly, clients are not required to always trust its value (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 7.4.1</a>). 4298 4298 </p> … … 4475 4475 <p id="rfc.section.E.2.p.1">Closed issues: </p> 4476 4476 <ul> 4477 <li> 4478 </li> 4479 <li> 4480 </li> 4481 <li> 4482 </li> 4483 <li> 4484 </li> 4485 <li> 4486 </li> 4487 <li> 4488 </li> 4489 <li> 4490 </li> 4491 <li> 4492 </li> 4493 <li> 4494 </li> 4495 <li> 4496 </li> 4497 <li> 4498 </li> 4499 <li> 4500 </li> 4501 <li> 4477 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/22">http://tools.ietf.org/wg/httpbis/trac/ticket/22</a>>: "ETag (and other metadata) in status messages" 4478 </li> 4479 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>>: "Conditional GET text" 4480 </li> 4481 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/146">http://tools.ietf.org/wg/httpbis/trac/ticket/146</a>>: "Clarify description of 405 (Not Allowed)" 4482 </li> 4483 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" 4484 </li> 4485 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/315">http://tools.ietf.org/wg/httpbis/trac/ticket/315</a>>: "method semantics: retrieval/representation" 4486 </li> 4487 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/388">http://tools.ietf.org/wg/httpbis/trac/ticket/388</a>>: "User confirmation for unsafe methods" 4488 </li> 4489 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/404">http://tools.ietf.org/wg/httpbis/trac/ticket/404</a>>: "Tentative Status Codes" 4490 </li> 4491 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>>: "No-Transform" 4492 </li> 4493 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>>: "p2 editorial feedback" 4494 </li> 4495 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/424">http://tools.ietf.org/wg/httpbis/trac/ticket/424</a>>: "Absence of Accept-Encoding" 4496 </li> 4497 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/428">http://tools.ietf.org/wg/httpbis/trac/ticket/428</a>>: "Accept-Language ordering for identical qvalues" 4498 </li> 4499 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/432">http://tools.ietf.org/wg/httpbis/trac/ticket/432</a>>: "Identify additional status codes as cacheable by default" 4500 </li> 4501 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/434">http://tools.ietf.org/wg/httpbis/trac/ticket/434</a>>: "mention in header field considerations that leading/trailing WS is lossy" 4502 4502 </li> 4503 4503 </ul> … … 4505 4505 <p id="rfc.section.E.3.p.1">Closed issues: </p> 4506 4506 <ul> 4507 <li> 4508 </li> 4509 <li> 4510 </li> 4511 <li> 4512 </li> 4513 <li> 4514 </li> 4515 <li> 4516 </li> 4517 <li> 4518 </li> 4519 <li> 4507 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 4508 </li> 4509 <li><<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448</a>>: "Fallback for Accept-Language" 4510 </li> 4511 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>>: "Receiving a higher minor HTTP version number" 4512 </li> 4513 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/456">http://tools.ietf.org/wg/httpbis/trac/ticket/456</a>>: "Language-tag vs. language-range" 4514 </li> 4515 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>>: "Registering x-gzip and x-deflate" 4516 </li> 4517 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/459">http://tools.ietf.org/wg/httpbis/trac/ticket/459</a>>: "RFC2774 and method registrations" 4518 </li> 4519 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/488">http://tools.ietf.org/wg/httpbis/trac/ticket/488</a>>: "Selection based upon request target" 4520 4520 </li> 4521 4521 </ul>
Note: See TracChangeset
for help on using the changeset viewer.
