Changeset 912
- Timestamp:
- 24/07/10 09:24:23 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 7 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r902 r912 685 685 </li> 686 686 <li class="tocline1">B.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li> 687 <li class="tocline1">B.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 688 <li class="tocline1">B.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 687 <li class="tocline1">B.3 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 689 688 </ul> 690 689 </li> … … 2954 2953 <p id="rfc.section.B.2.p.3">The original HTTP/1.0 form of persistent connections (the Connection: Keep-Alive and Keep-Alive header) is documented in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 2955 2954 </p> 2956 <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 2957 <p id="rfc.section.B.3.p.1">This specification has been carefully audited to correct and disambiguate key word usage; RFC 2068 had many problems in respect 2958 to the conventions laid out in <a href="#RFC2119" id="rfc.xref.RFC2119.2"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>. 2959 </p> 2960 <p id="rfc.section.B.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 2961 for transfer encoding that might not be self delimiting); it was important to straighten out exactly how message lengths are 2962 computed. (Sections <a href="#transfer.codings" title="Transfer Codings">6.2</a>, <a href="#message.body" title="Message Body">3.3</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">9.2</a>, see also <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) 2963 </p> 2964 <p id="rfc.section.B.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0 2965 implementations (<a href="#http.version" title="HTTP Version">Section 2.5</a>) 2966 </p> 2967 <p id="rfc.section.B.3.p.4">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section 6.4</a>) 2968 </p> 2969 <p id="rfc.section.B.3.p.5">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings 2970 become as full fledged as content-codings. This involves adding an IANA registry for transfer-codings (separate from content 2971 codings), a new header field (TE) and enabling trailer headers in the future. Transfer encoding is a major performance benefit, 2972 so it was worth fixing <a href="#Nie1997" id="rfc.xref.Nie1997.2"><cite title="Network Performance Effects of HTTP/1.1, CSS1, and PNG">[Nie1997]</cite></a>. TE also solves another, obscure, downward interoperability problem that could have occurred due to interactions between 2973 authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">6.2</a>, <a href="#chunked.encoding" title="Chunked Transfer Coding">6.2.1</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">7.1.3.2</a>, and <a href="#header.te" id="rfc.xref.header.te.5" title="TE">9.5</a>) 2974 </p> 2975 <p id="rfc.section.B.3.p.6">Proxies should be able to add Content-Length when appropriate. (<a href="#non-modifiable.headers" title="Non-modifiable Headers">Section 7.1.3.2</a>) 2976 </p> 2977 <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 2978 <p id="rfc.section.B.4.p.1">Empty list elements in list productions have been deprecated. (<a href="#notation.abnf" title="ABNF Extension: #rule">Section 1.2.1</a>) 2979 </p> 2980 <p id="rfc.section.B.4.p.2">Rules about implicit linear whitespace between certain grammar productions have been removed; now it's only allowed when specifically 2955 <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 2956 <p id="rfc.section.B.3.p.1">Empty list elements in list productions have been deprecated. (<a href="#notation.abnf" title="ABNF Extension: #rule">Section 1.2.1</a>) 2957 </p> 2958 <p id="rfc.section.B.3.p.2">Rules about implicit linear whitespace between certain grammar productions have been removed; now it's only allowed when specifically 2981 2959 pointed out in the ABNF. The NUL character is no longer allowed in comment and quoted-string text. The quoted-pair rule no 2982 2960 longer allows escaping control characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted 2983 2961 and made opaque (the TEXT rule was removed) (<a href="#basic.rules" title="Basic Rules">Section 1.2.2</a>) 2984 2962 </p> 2985 <p id="rfc.section.B. 4.p.3">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section 2.5</a>)2986 </p> 2987 <p id="rfc.section.B. 4.p.4">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#transfer.codings" title="Transfer Codings">6.2</a> and <a href="#message.body" title="Message Body">3.3</a>)2988 </p> 2989 <p id="rfc.section.B. 4.p.5">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section 3.2</a>)2990 </p> 2991 <p id="rfc.section.B. 4.p.6">Update use of abs_path production from RFC1808 to the path-absolute + query components of RFC3986. (<a href="#request-target" title="request-target">Section 4.1.2</a>)2992 </p> 2993 <p id="rfc.section.B. 4.p.7">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore2963 <p id="rfc.section.B.3.p.3">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section 2.5</a>) 2964 </p> 2965 <p id="rfc.section.B.3.p.4">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#transfer.codings" title="Transfer Codings">6.2</a> and <a href="#message.body" title="Message Body">3.3</a>) 2966 </p> 2967 <p id="rfc.section.B.3.p.5">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 2968 </p> 2969 <p id="rfc.section.B.3.p.6">Update use of abs_path production from RFC1808 to the path-absolute + query components of RFC3986. (<a href="#request-target" title="request-target">Section 4.1.2</a>) 2970 </p> 2971 <p id="rfc.section.B.3.p.7">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore 2994 2972 disallowed line folding in chunk extensions. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 6.2.1</a>) 2995 2973 </p> 2996 <p id="rfc.section.B. 4.p.8">Remove hard limit of two connections per server. (<a href="#persistent.practical" title="Practical Considerations">Section 7.1.4</a>)2997 </p> 2998 <p id="rfc.section.B. 4.p.9">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.9" title="Connection">Section 9.1</a>)2974 <p id="rfc.section.B.3.p.8">Remove hard limit of two connections per server. (<a href="#persistent.practical" title="Practical Considerations">Section 7.1.4</a>) 2975 </p> 2976 <p id="rfc.section.B.3.p.9">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.9" title="Connection">Section 9.1</a>) 2999 2977 </p> 3000 2978 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 3461 3439 </li> 3462 3440 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/159">http://tools.ietf.org/wg/httpbis/trac/ticket/159</a>>: "HTTP(s) URI scheme definitions" 3441 </li> 3442 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" 3463 3443 </li> 3464 3444 </ul> … … 3491 3471 <li class="indline1">compress (Coding Format) <a class="iref" href="#rfc.iref.c.7">6.2.2.1</a></li> 3492 3472 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.2">2.1</a></li> 3493 <li class="indline1">Connection header <a class="iref" href="#rfc.xref.header.connection.1">3.4</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.xref.header.connection.4">7.1.3.1</a>, <a class="iref" href="#rfc.iref.c.11"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.5">9.5</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.8</a>, <a class="iref" href="#rfc.xref.header.connection.7">10.1</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.9">B. 4</a></li>3494 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">3.3</a>, <a class="iref" href="#rfc.iref.c.12"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">10.1</a> , <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>3473 <li class="indline1">Connection header <a class="iref" href="#rfc.xref.header.connection.1">3.4</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.xref.header.connection.4">7.1.3.1</a>, <a class="iref" href="#rfc.iref.c.11"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.5">9.5</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.8</a>, <a class="iref" href="#rfc.xref.header.connection.7">10.1</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.9">B.3</a></li> 3474 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">3.3</a>, <a class="iref" href="#rfc.iref.c.12"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">10.1</a></li> 3495 3475 </ul> 3496 3476 </li> … … 3638 3618 <li class="indline1">Headers 3639 3619 <ul class="ind"> 3640 <li class="indline1">Connection <a class="iref" href="#rfc.xref.header.connection.1">3.4</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.xref.header.connection.4">7.1.3.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.5">9.5</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.8</a>, <a class="iref" href="#rfc.xref.header.connection.7">10.1</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.9">B. 4</a></li>3641 <li class="indline1">Content-Length <a class="iref" href="#rfc.xref.header.content-length.1">3.3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">10.1</a> , <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>3620 <li class="indline1">Connection <a class="iref" href="#rfc.xref.header.connection.1">3.4</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.xref.header.connection.4">7.1.3.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.5">9.5</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.8</a>, <a class="iref" href="#rfc.xref.header.connection.7">10.1</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.9">B.3</a></li> 3621 <li class="indline1">Content-Length <a class="iref" href="#rfc.xref.header.content-length.1">3.3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">10.1</a></li> 3642 3622 <li class="indline1">Date <a class="iref" href="#rfc.xref.header.date.1">3.4</a>, <a class="iref" href="#rfc.iref.h.8"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">10.1</a></li> 3643 3623 <li class="indline1">Host <a class="iref" href="#rfc.xref.header.host.1">4.3</a>, <a class="iref" href="#rfc.iref.h.10"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.host.2">10.1</a>, <a class="iref" href="#rfc.xref.header.host.3">B.1.1</a></li> 3644 <li class="indline1">TE <a class="iref" href="#rfc.xref.header.te.1">6.2</a>, <a class="iref" href="#rfc.xref.header.te.2">6.2.1</a>, <a class="iref" href="#rfc.xref.header.te.3">6.4</a>, <a class="iref" href="#rfc.iref.h.11"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">10.1</a> , <a class="iref" href="#rfc.xref.header.te.5">B.3</a></li>3624 <li class="indline1">TE <a class="iref" href="#rfc.xref.header.te.1">6.2</a>, <a class="iref" href="#rfc.xref.header.te.2">6.2.1</a>, <a class="iref" href="#rfc.xref.header.te.3">6.4</a>, <a class="iref" href="#rfc.iref.h.11"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">10.1</a></li> 3645 3625 <li class="indline1">Trailer <a class="iref" href="#rfc.xref.header.trailer.1">3.4</a>, <a class="iref" href="#rfc.xref.header.trailer.2">6.2.1</a>, <a class="iref" href="#rfc.iref.h.12"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">10.1</a></li> 3646 3626 <li class="indline1">Transfer-Encoding <a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">3.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">6.2</a>, <a class="iref" href="#rfc.iref.h.13"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">10.1</a></li> … … 3675 3655 </li> 3676 3656 <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind"> 3677 <li class="indline1"><em>Nie1997</em> <a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>13.2</b></a> , <a class="iref" href="#rfc.xref.Nie1997.2">B.3</a></li>3657 <li class="indline1"><em>Nie1997</em> <a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>13.2</b></a></li> 3678 3658 </ul> 3679 3659 </li> … … 3704 3684 </ul> 3705 3685 </li> 3706 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>13.1</b></a> , <a class="iref" href="#rfc.xref.Part5.1">B.3</a></li>3686 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>13.1</b></a></li> 3707 3687 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.5">3.3</a>, <a class="iref" href="#rfc.xref.Part6.6">3.4</a>, <a class="iref" href="#rfc.xref.Part6.7">3.4</a>, <a class="iref" href="#rfc.xref.Part6.8">3.4</a>, <a class="iref" href="#rfc.xref.Part6.9">7.1.3.2</a>, <a class="iref" href="#Part6"><b>13.1</b></a><ul class="ind"> 3708 3688 <li class="indline1"><em>Section 2</em> <a class="iref" href="#rfc.xref.Part6.4">2.3</a></li> … … 3738 3718 </li> 3739 3719 <li class="indline1"><em>RFC2109</em> <a class="iref" href="#rfc.xref.RFC2109.1">3.2</a>, <a class="iref" href="#RFC2109"><b>13.2</b></a></li> 3740 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>13.1</b></a> , <a class="iref" href="#rfc.xref.RFC2119.2">B.3</a></li>3741 <li class="indline1"><em>RFC2145</em> <a class="iref" href="#rfc.xref.RFC2145.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2145.2">2.5</a>, <a class="iref" href="#RFC2145"><b>13.2</b></a> , <a class="iref" href="#rfc.xref.RFC2145.3">B.3</a></li>3720 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>13.1</b></a></li> 3721 <li class="indline1"><em>RFC2145</em> <a class="iref" href="#rfc.xref.RFC2145.1">2.5</a>, <a class="iref" href="#rfc.xref.RFC2145.2">2.5</a>, <a class="iref" href="#RFC2145"><b>13.2</b></a></li> 3742 3722 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">12</a>, <a class="iref" href="#RFC2616"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">D.1</a></li> 3743 3723 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">10.5</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a><ul class="ind"> … … 3787 3767 </li> 3788 3768 <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind"> 3789 <li class="indline1">TE header <a class="iref" href="#rfc.xref.header.te.1">6.2</a>, <a class="iref" href="#rfc.xref.header.te.2">6.2.1</a>, <a class="iref" href="#rfc.xref.header.te.3">6.4</a>, <a class="iref" href="#rfc.iref.t.2"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">10.1</a> , <a class="iref" href="#rfc.xref.header.te.5">B.3</a></li>3769 <li class="indline1">TE header <a class="iref" href="#rfc.xref.header.te.1">6.2</a>, <a class="iref" href="#rfc.xref.header.te.2">6.2.1</a>, <a class="iref" href="#rfc.xref.header.te.3">6.4</a>, <a class="iref" href="#rfc.iref.t.2"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.te.4">10.1</a></li> 3790 3770 <li class="indline1"><em>Tou1998</em> <a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>13.2</b></a></li> 3791 3771 <li class="indline1">Trailer header <a class="iref" href="#rfc.xref.header.trailer.1">3.4</a>, <a class="iref" href="#rfc.xref.header.trailer.2">6.2.1</a>, <a class="iref" href="#rfc.iref.t.3"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">10.1</a></li> -
draft-ietf-httpbis/latest/p2-semantics.html
r902 r912 388 388 <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12"> 389 389 <link rel="Chapter" href="#rfc.section.13" title="13 References"> 390 <link rel="Appendix" title="A C ompatibility with Previous Versions" href="#rfc.section.A">390 <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A"> 391 391 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 392 392 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> … … 661 661 </li> 662 662 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> 663 <li class="tocline0">A. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 664 <li class="tocline1">A.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 665 <li class="tocline1">A.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 666 </ul> 667 </li> 663 <li class="tocline0">A. <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 668 664 <li class="tocline0">B. <a href="#collected.abnf">Collected ABNF</a></li> 669 665 <li class="tocline0">C. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> … … 1043 1039 a Location header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 9.4</a>). 1044 1040 </p> 1045 <p id="rfc.section.7.5.p.5">Responses to POST requests are cacheable only when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). Such cached POST responses <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests. Note that POST caching is not widely implemented. However, the 303 (See 1046 Other) response can be used to direct the user agent to retrieve a cacheable resource. 1041 <p id="rfc.section.7.5.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header (see <a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) whose value is the Effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests. 1042 </p> 1043 <p id="rfc.section.7.5.p.6">Note that POST caching is not widely implemented. However, the 303 (See Other) response can be used to direct the user agent 1044 to retrieve a cacheable resource. 1047 1045 </p> 1048 1046 <div id="rfc.iref.p.2"></div> … … 1236 1234 <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 1237 1235 <p id="rfc.section.8.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven 1238 negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.1 0"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that1236 negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that 1239 1237 location. 1240 1238 </p> … … 1311 1309 <div id="rfc.iref.s.16"></div> 1312 1310 <h3 id="rfc.section.8.3.6"><a href="#rfc.section.8.3.6">8.3.6</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 1313 <p id="rfc.section.8.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix A .2</a>), and is now deprecated.1311 <p id="rfc.section.8.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix A</a>), and is now deprecated. 1314 1312 </p> 1315 1313 <div id="rfc.iref.40"></div> … … 1617 1615 </div> 1618 1616 <div class="note" id="rfc.section.9.4.p.9"> 1619 <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.1 1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.1617 <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation. 1620 1618 It is therefore possible for a response to contain header fields for both Location and Content-Location. 1621 1619 </p> … … 2253 2251 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 2254 2252 </div> 2255 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 2256 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 2257 <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g., DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section 8.5.5</a>). 2258 </p> 2259 <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an ETag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section 8.2.2</a>). 2260 </p> 2261 <p id="rfc.section.A.1.p.3">303 (See Also) and 307 (Temporary Redirect) added to address user agent failure to implement status code 302 properly. (Section <a href="#status.303" id="rfc.xref.status.303.4" title="303 See Other">8.3.4</a> and <a href="#status.307" id="rfc.xref.status.307.4" title="307 Temporary Redirect">8.3.8</a>) 2262 </p> 2263 <p id="rfc.section.A.1.p.4">Rewrite of message transmission requirements to make it much harder for implementors to get it wrong, as the consequences 2264 of errors here can have significant impact on the Internet, and to deal with the following problems: 2265 </p> 2266 <ol> 2267 <li>Changing "HTTP/1.1 or later" to "HTTP/1.1", in contexts where this was incorrectly placing a requirement on the behavior of 2268 an implementation of a future version of HTTP/1.x 2269 </li> 2270 <li>Made it clear that user-agents should retry requests, not "clients" in general.</li> 2271 <li>Converted requirements for clients to ignore unexpected 100 (Continue) responses, and for proxies to forward 100 responses, 2272 into a general requirement for 1xx responses. 2273 </li> 2274 <li>Modified some TCP-specific language, to make it clearer that non-TCP transports are possible for HTTP.</li> 2275 <li>Require that the origin server <em class="bcp14">MUST NOT</em> wait for the request body before it sends a required 100 (Continue) response. 2276 </li> 2277 <li>Allow, rather than require, a server to omit 100 (Continue) if it has already seen some of the request body.</li> 2278 <li>Allow servers to defend against denial-of-service attacks and broken clients.</li> 2279 </ol> 2280 <p id="rfc.section.A.1.p.5">This change adds the Expect header and 417 status code.</p> 2281 <p id="rfc.section.A.1.p.6">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">8.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">8.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">8.4.11</a>) 2282 </p> 2283 <p id="rfc.section.A.1.p.7">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 2284 </p> 2285 <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> 2286 <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.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 4.1</a>) 2287 </p> 2288 <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section 7.5</a>) 2289 </p> 2290 <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 2291 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">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.5" title="307 Temporary Redirect">8.3.8</a>) 2292 </p> 2293 <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 2253 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 2254 <p id="rfc.section.A.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.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 4.1</a>) 2255 </p> 2256 <p id="rfc.section.A.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section 7.5</a>) 2257 </p> 2258 <p id="rfc.section.A.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 2259 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">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.4" title="307 Temporary Redirect">8.3.8</a>) 2260 </p> 2261 <p id="rfc.section.A.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource 2294 2262 must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient 2295 2263 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 8.3.6</a>) 2296 2264 </p> 2297 <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 requirement2265 <p id="rfc.section.A.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement 2298 2266 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 9.1</a>) 2299 2267 </p> 2300 <p id="rfc.section.A. 2.p.6">Correct syntax of Location header to allow URI references (including relative references and fragments), as referred symbol2268 <p id="rfc.section.A.p.6">Correct syntax of Location header to allow URI references (including relative references and fragments), as referred symbol 2301 2269 "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate. 2302 2270 (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.4</a>) 2303 2271 </p> 2304 <p id="rfc.section.A. 2.p.7">Allow Referer value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.6</a>)2305 </p> 2306 <p id="rfc.section.A. 2.p.8">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly2272 <p id="rfc.section.A.p.7">Allow Referer value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.6</a>) 2273 </p> 2274 <p id="rfc.section.A.p.8">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 2307 2275 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.34"><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 9.8</a>) 2308 2276 </p> … … 2605 2573 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/199">http://tools.ietf.org/wg/httpbis/trac/ticket/199</a>>: "Status codes and caching" 2606 2574 </li> 2575 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" 2576 </li> 2607 2577 </ul> 2608 2578 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 2618 2588 <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind"> 2619 2589 <li class="indline1">200 OK (status code) <a class="iref" href="#rfc.xref.status.200.1">4</a>, <a class="iref" href="#rfc.iref.27"><b>8.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">10.2</a></li> 2620 <li class="indline1">201 Created (status code) <a class="iref" href="#rfc.xref.status.201.1">4</a>, <a class="iref" href="#rfc.iref.28"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">10.2</a> , <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>2590 <li class="indline1">201 Created (status code) <a class="iref" href="#rfc.xref.status.201.1">4</a>, <a class="iref" href="#rfc.iref.28"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">10.2</a></li> 2621 2591 <li class="indline1">202 Accepted (status code) <a class="iref" href="#rfc.xref.status.202.1">4</a>, <a class="iref" href="#rfc.iref.29"><b>8.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">10.2</a></li> 2622 2592 <li class="indline1">203 Non-Authoritative Information (status code) <a class="iref" href="#rfc.xref.status.203.1">4</a>, <a class="iref" href="#rfc.iref.30"><b>8.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">10.2</a></li> … … 2628 2598 <li class="indline0"><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul class="ind"> 2629 2599 <li class="indline1">300 Multiple Choices (status code) <a class="iref" href="#rfc.xref.status.300.1">4</a>, <a class="iref" href="#rfc.iref.34"><b>8.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">10.2</a></li> 2630 <li class="indline1">301 Moved Permanently (status code) <a class="iref" href="#rfc.xref.status.301.1">4</a>, <a class="iref" href="#rfc.iref.35"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">10.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A .2</a></li>2631 <li class="indline1">302 Found (status code) <a class="iref" href="#rfc.xref.status.302.1">4</a>, <a class="iref" href="#rfc.iref.36"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">10.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A .2</a></li>2632 <li class="indline1">303 See Other (status code) <a class="iref" href="#rfc.xref.status.303.1">4</a>, <a class="iref" href="#rfc.xref.status.303.2">8.3.3</a>, <a class="iref" href="#rfc.iref.37"><b>8.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.3">10.2</a> , <a class="iref" href="#rfc.xref.status.303.4">A.1</a></li>2600 <li class="indline1">301 Moved Permanently (status code) <a class="iref" href="#rfc.xref.status.301.1">4</a>, <a class="iref" href="#rfc.iref.35"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">10.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A</a></li> 2601 <li class="indline1">302 Found (status code) <a class="iref" href="#rfc.xref.status.302.1">4</a>, <a class="iref" href="#rfc.iref.36"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">10.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A</a></li> 2602 <li class="indline1">303 See Other (status code) <a class="iref" href="#rfc.xref.status.303.1">4</a>, <a class="iref" href="#rfc.xref.status.303.2">8.3.3</a>, <a class="iref" href="#rfc.iref.37"><b>8.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.3">10.2</a></li> 2633 2603 <li class="indline1">304 Not Modified (status code) <a class="iref" href="#rfc.iref.38"><b>8.3.5</b></a></li> 2634 <li class="indline1">305 Use Proxy (status code) <a class="iref" href="#rfc.xref.status.305.1">4</a>, <a class="iref" href="#rfc.iref.39"><b>8.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">10.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A .2</a></li>2604 <li class="indline1">305 Use Proxy (status code) <a class="iref" href="#rfc.xref.status.305.1">4</a>, <a class="iref" href="#rfc.iref.39"><b>8.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">10.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A</a></li> 2635 2605 <li class="indline1">306 (Unused) (status code) <a class="iref" href="#rfc.iref.40"><b>8.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">10.2</a></li> 2636 <li class="indline1">307 Temporary Redirect (status code) <a class="iref" href="#rfc.xref.status.307.1">4</a>, <a class="iref" href="#rfc.xref.status.307.2">8.3.3</a>, <a class="iref" href="#rfc.iref.41"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.3">10.2</a>, <a class="iref" href="#rfc.xref.status.307.4">A .1</a>, <a class="iref" href="#rfc.xref.status.307.5">A.2</a></li>2606 <li class="indline1">307 Temporary Redirect (status code) <a class="iref" href="#rfc.xref.status.307.1">4</a>, <a class="iref" href="#rfc.xref.status.307.2">8.3.3</a>, <a class="iref" href="#rfc.iref.41"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.3">10.2</a>, <a class="iref" href="#rfc.xref.status.307.4">A</a></li> 2637 2607 </ul> 2638 2608 </li> … … 2641 2611 <li class="indline1">401 Unauthorized (status code) <a class="iref" href="#rfc.iref.43"><b>8.4.2</b></a></li> 2642 2612 <li class="indline1">402 Payment Required (status code) <a class="iref" href="#rfc.xref.status.402.1">4</a>, <a class="iref" href="#rfc.iref.44"><b>8.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">10.2</a></li> 2643 <li class="indline1">403 Forbidden (status code) <a class="iref" href="#rfc.xref.status.403.1">4</a>, <a class="iref" href="#rfc.iref.45"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">10.2</a> , <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>2644 <li class="indline1">404 Not Found (status code) <a class="iref" href="#rfc.xref.status.404.1">4</a>, <a class="iref" href="#rfc.iref.46"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">10.2</a> , <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>2613 <li class="indline1">403 Forbidden (status code) <a class="iref" href="#rfc.xref.status.403.1">4</a>, <a class="iref" href="#rfc.iref.45"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">10.2</a></li> 2614 <li class="indline1">404 Not Found (status code) <a class="iref" href="#rfc.xref.status.404.1">4</a>, <a class="iref" href="#rfc.iref.46"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">10.2</a></li> 2645 2615 <li class="indline1">405 Method Not Allowed (status code) <a class="iref" href="#rfc.xref.status.405.1">4</a>, <a class="iref" href="#rfc.iref.47"><b>8.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">10.2</a></li> 2646 2616 <li class="indline1">406 Not Acceptable (status code) <a class="iref" href="#rfc.xref.status.406.1">4</a>, <a class="iref" href="#rfc.iref.48"><b>8.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">10.2</a></li> … … 2648 2618 <li class="indline1">408 Request Timeout (status code) <a class="iref" href="#rfc.xref.status.408.1">4</a>, <a class="iref" href="#rfc.iref.50"><b>8.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">10.2</a></li> 2649 2619 <li class="indline1">409 Conflict (status code) <a class="iref" href="#rfc.xref.status.409.1">4</a>, <a class="iref" href="#rfc.iref.51"><b>8.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">10.2</a></li> 2650 <li class="indline1">410 Gone (status code) <a class="iref" href="#rfc.xref.status.410.1">4</a>, <a class="iref" href="#rfc.iref.52"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">10.2</a> , <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>2620 <li class="indline1">410 Gone (status code) <a class="iref" href="#rfc.xref.status.410.1">4</a>, <a class="iref" href="#rfc.iref.52"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">10.2</a></li> 2651 2621 <li class="indline1">411 Length Required (status code) <a class="iref" href="#rfc.xref.status.411.1">4</a>, <a class="iref" href="#rfc.iref.53"><b>8.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">10.2</a></li> 2652 2622 <li class="indline1">412 Precondition Failed (status code) <a class="iref" href="#rfc.iref.54"><b>8.4.13</b></a></li> … … 2663 2633 <li class="indline1">502 Bad Gateway (status code) <a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.62"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li> 2664 2634 <li class="indline1">503 Service Unavailable (status code) <a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.63"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li> 2665 <li class="indline1">504 Gateway Timeout (status code) <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.64"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a> , <a class="iref" href="#rfc.xref.status.504.3">A.1</a></li>2635 <li class="indline1">504 Gateway Timeout (status code) <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.64"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a></li> 2666 2636 <li class="indline1">505 HTTP Version Not Supported (status code) <a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.65"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li> 2667 2637 </ul> 2668 2638 </li> 2669 2639 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 2670 <li class="indline1">Allow header <a class="iref" href="#rfc.xref.header.allow.1">2</a>, <a class="iref" href="#rfc.xref.header.allow.2">5</a>, <a class="iref" href="#rfc.iref.a.1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">10.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A .2</a></li>2640 <li class="indline1">Allow header <a class="iref" href="#rfc.xref.header.allow.1">2</a>, <a class="iref" href="#rfc.xref.header.allow.2">5</a>, <a class="iref" href="#rfc.iref.a.1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">10.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A</a></li> 2671 2641 </ul> 2672 2642 </li> … … 2728 2698 <li class="indline1">Headers 2729 2699 <ul class="ind"> 2730 <li class="indline1">Allow <a class="iref" href="#rfc.xref.header.allow.1">2</a>, <a class="iref" href="#rfc.xref.header.allow.2">5</a>, <a class="iref" href="#rfc.iref.h.2"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">10.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A .2</a></li>2700 <li class="indline1">Allow <a class="iref" href="#rfc.xref.header.allow.1">2</a>, <a class="iref" href="#rfc.xref.header.allow.2">5</a>, <a class="iref" href="#rfc.iref.h.2"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">10.3</a>, <a class="iref" href="#rfc.xref.header.allow.4">A</a></li> 2731 2701 <li class="indline1">Expect <a class="iref" href="#rfc.xref.header.expect.1">3</a>, <a class="iref" href="#rfc.xref.header.expect.2">8.4.18</a>, <a class="iref" href="#rfc.iref.h.3"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.header.expect.3">10.3</a></li> 2732 2702 <li class="indline1">From <a class="iref" href="#rfc.xref.header.from.1">3</a>, <a class="iref" href="#rfc.iref.h.4"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.header.from.2">10.3</a></li> 2733 <li class="indline1">Location <a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A .2</a></li>2703 <li class="indline1">Location <a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A</a></li> 2734 2704 <li class="indline1">Max-Forwards <a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.2</a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">7.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.4">10.3</a></li> 2735 <li class="indline1">Referer <a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a>, <a class="iref" href="#rfc.xref.header.referer.3">A .2</a></li>2705 <li class="indline1">Referer <a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a>, <a class="iref" href="#rfc.xref.header.referer.3">A</a></li> 2736 2706 <li class="indline1">Retry-After <a class="iref" href="#rfc.xref.header.retry-after.1">5</a>, <a class="iref" href="#rfc.iref.h.8"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">10.3</a></li> 2737 <li class="indline1">Server <a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.h.9"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A .2</a></li>2707 <li class="indline1">Server <a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.h.9"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A</a></li> 2738 2708 <li class="indline1">User-Agent <a class="iref" href="#rfc.xref.header.user-agent.1">3</a>, <a class="iref" href="#rfc.iref.h.10"><b>9.9</b></a>, <a class="iref" href="#rfc.xref.header.user-agent.2">10.3</a>, <a class="iref" href="#rfc.xref.header.user-agent.3">11.1</a></li> 2739 2709 </ul> … … 2746 2716 </li> 2747 2717 <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind"> 2748 <li class="indline1">LINK method <a class="iref" href="#rfc.iref.l.2"><b>A.1</b></a></li> 2749 <li class="indline1">Location header <a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A.2</a></li> 2718 <li class="indline1">Location header <a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A</a></li> 2750 2719 </ul> 2751 2720 </li> … … 2758 2727 <li class="indline1">GET <a class="iref" href="#rfc.xref.GET.1">2</a>, <a class="iref" href="#rfc.iref.m.2"><b>7.3</b></a>, <a class="iref" href="#rfc.xref.GET.2">10.1</a></li> 2759 2728 <li class="indline1">HEAD <a class="iref" href="#rfc.xref.HEAD.1">2</a>, <a class="iref" href="#rfc.iref.m.3"><b>7.4</b></a>, <a class="iref" href="#rfc.xref.HEAD.2">10.1</a></li> 2760 <li class="indline1">LINK <a class="iref" href="#rfc.iref.m.11"><b>A.1</b></a></li>2761 2729 <li class="indline1">OPTIONS <a class="iref" href="#rfc.xref.OPTIONS.1">2</a>, <a class="iref" href="#rfc.iref.m.1"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.OPTIONS.2">9.5</a>, <a class="iref" href="#rfc.xref.OPTIONS.3">10.1</a></li> 2762 <li class="indline1">PATCH <a class="iref" href="#rfc.iref.m.10"><b>A.1</b></a></li> 2763 <li class="indline1">POST <a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.m.4"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li> 2730 <li class="indline1">POST <a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.m.4"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A</a></li> 2764 2731 <li class="indline1">PUT <a class="iref" href="#rfc.xref.PUT.1">2</a>, <a class="iref" href="#rfc.iref.m.5"><b>7.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">10.1</a></li> 2765 2732 <li class="indline1">TRACE <a class="iref" href="#rfc.xref.TRACE.1">2</a>, <a class="iref" href="#rfc.iref.m.7"><b>7.8</b></a>, <a class="iref" href="#rfc.xref.TRACE.2">9.5</a>, <a class="iref" href="#rfc.xref.TRACE.3">10.1</a>, <a class="iref" href="#rfc.xref.TRACE.4">11.1</a></li> 2766 <li class="indline1">UNLINK <a class="iref" href="#rfc.iref.m.12"><b>A.1</b></a></li>2767 2733 </ul> 2768 2734 </li> … … 2774 2740 </li> 2775 2741 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 2776 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">3</a>, <a class="iref" href="#rfc.xref.Part1.19">3</a>, <a class="iref" href="#rfc.xref.Part1.20">5</a>, <a class="iref" href="#rfc.xref.Part1.21">6</a>, <a class="iref" href="#rfc.xref.Part1.22">6.1</a>, <a class="iref" href="#rfc.xref.Part1.23">7.8</a>, <a class="iref" href="#rfc.xref.Part1.24">7.8</a>, <a class="iref" href="#rfc.xref.Part1.25">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.26">8.1.2</a>, <a class="iref" href="#rfc.xref.Part1.27">8.5.6</a>, <a class="iref" href="#rfc.xref.Part1.28">9.2</a>, <a class="iref" href="#rfc.xref.Part1.29">9.8</a>, <a class="iref" href="#rfc.xref.Part1.30">9.8</a>, <a class="iref" href="#rfc.xref.Part1.31">9.8</a>, <a class="iref" href="#rfc.xref.Part1.32">9.9</a>, <a class="iref" href="#rfc.xref.Part1.33">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.34">A .2</a><ul class="ind">2742 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">3</a>, <a class="iref" href="#rfc.xref.Part1.19">3</a>, <a class="iref" href="#rfc.xref.Part1.20">5</a>, <a class="iref" href="#rfc.xref.Part1.21">6</a>, <a class="iref" href="#rfc.xref.Part1.22">6.1</a>, <a class="iref" href="#rfc.xref.Part1.23">7.8</a>, <a class="iref" href="#rfc.xref.Part1.24">7.8</a>, <a class="iref" href="#rfc.xref.Part1.25">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.26">8.1.2</a>, <a class="iref" href="#rfc.xref.Part1.27">8.5.6</a>, <a class="iref" href="#rfc.xref.Part1.28">9.2</a>, <a class="iref" href="#rfc.xref.Part1.29">9.8</a>, <a class="iref" href="#rfc.xref.Part1.30">9.8</a>, <a class="iref" href="#rfc.xref.Part1.31">9.8</a>, <a class="iref" href="#rfc.xref.Part1.32">9.9</a>, <a class="iref" href="#rfc.xref.Part1.33">9.9</a>, <a class="iref" href="#Part1"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part1.34">A</a><ul class="ind"> 2777 2743 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2</a></li> 2778 2744 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a></li> … … 2788 2754 <li class="indline1"><em>Section 9.5</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.19">3</a></li> 2789 2755 <li class="indline1"><em>Section 9.8</em> <a class="iref" href="#rfc.xref.Part1.26">8.1.2</a></li> 2790 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part1.23">7.8</a>, <a class="iref" href="#rfc.xref.Part1.31">9.8</a>, <a class="iref" href="#rfc.xref.Part1.34">A .2</a></li>2756 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part1.23">7.8</a>, <a class="iref" href="#rfc.xref.Part1.31">9.8</a>, <a class="iref" href="#rfc.xref.Part1.34">A</a></li> 2791 2757 <li class="indline1"><em>Section 10.3.1</em> <a class="iref" href="#rfc.xref.Part1.24">7.8</a></li> 2792 2758 </ul> 2793 2759 </li> 2794 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#rfc.xref.Part3.10"> 8.3.1</a>, <a class="iref" href="#rfc.xref.Part3.11">9.4</a>, <a class="iref" href="#Part3"><b>13.1</b></a><ul class="ind">2795 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.1 0">8.3.1</a></li>2760 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#rfc.xref.Part3.10">7.5</a>, <a class="iref" href="#rfc.xref.Part3.11">8.3.1</a>, <a class="iref" href="#rfc.xref.Part3.12">9.4</a>, <a class="iref" href="#Part3"><b>13.1</b></a><ul class="ind"> 2761 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.11">8.3.1</a></li> 2796 2762 <li class="indline1"><em>Section 5.1</em> <a class="iref" href="#rfc.xref.Part3.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.5">3</a></li> 2797 2763 <li class="indline1"><em>Section 5.2</em> <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3</a></li> 2798 2764 <li class="indline1"><em>Section 5.3</em> <a class="iref" href="#rfc.xref.Part3.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.7">3</a></li> 2799 2765 <li class="indline1"><em>Section 5.4</em> <a class="iref" href="#rfc.xref.Part3.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.8">3</a></li> 2800 <li class="indline1"><em>Section 5.7</em> <a class="iref" href="#rfc.xref.Part3.1 1">9.4</a></li>2766 <li class="indline1"><em>Section 5.7</em> <a class="iref" href="#rfc.xref.Part3.10">7.5</a>, <a class="iref" href="#rfc.xref.Part3.12">9.4</a></li> 2801 2767 </ul> 2802 2768 </li> … … 2839 2805 </ul> 2840 2806 </li> 2841 <li class="indline1">PATCH method <a class="iref" href="#rfc.iref.p.3"><b>A.1</b></a></li> 2842 <li class="indline1">POST method <a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.p.1"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A.2</a></li> 2807 <li class="indline1">POST method <a class="iref" href="#rfc.xref.POST.1">2</a>, <a class="iref" href="#rfc.iref.p.1"><b>7.5</b></a>, <a class="iref" href="#rfc.xref.POST.2">10.1</a>, <a class="iref" href="#rfc.xref.POST.3">A</a></li> 2843 2808 <li class="indline1">PUT method <a class="iref" href="#rfc.xref.PUT.1">2</a>, <a class="iref" href="#rfc.iref.p.2"><b>7.6</b></a>, <a class="iref" href="#rfc.xref.PUT.2">10.1</a></li> 2844 2809 </ul> 2845 2810 </li> 2846 2811 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 2847 <li class="indline1">Referer header <a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.r.1"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a>, <a class="iref" href="#rfc.xref.header.referer.3">A .2</a></li>2812 <li class="indline1">Referer header <a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.r.1"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a>, <a class="iref" href="#rfc.xref.header.referer.3">A</a></li> 2848 2813 <li class="indline1">Retry-After header <a class="iref" href="#rfc.xref.header.retry-after.1">5</a>, <a class="iref" href="#rfc.iref.r.2"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">10.3</a></li> 2849 2814 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">8.3.3</a>, <a class="iref" href="#RFC1945"><b>13.2</b></a><ul class="ind"> … … 2851 2816 </ul> 2852 2817 </li> 2853 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a>, <a class="iref" href="#RFC2068"><b>13.2</b></a> , <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a><ul class="ind">2818 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3</a>, <a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a>, <a class="iref" href="#RFC2068"><b>13.2</b></a><ul class="ind"> 2854 2819 <li class="indline1"><em>Section 10.3</em> <a class="iref" href="#rfc.xref.RFC2068.1">8.3</a></li> 2855 2820 <li class="indline1"><em>Section 10.3.3</em> <a class="iref" href="#rfc.xref.RFC2068.2">8.3.3</a></li> 2856 <li class="indline1"><em>Section 19.6.1</em> <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>2857 2821 </ul> 2858 2822 </li> … … 2862 2826 </ul> 2863 2827 </li> 2864 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">7.9</a>, <a class="iref" href="#rfc.xref.RFC2817.2">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.3">A .2</a><ul class="ind">2865 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.RFC2817.2">10.2</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A .2</a></li>2828 <li class="indline1"><em>RFC2817</em> <a class="iref" href="#rfc.xref.RFC2817.1">7.9</a>, <a class="iref" href="#rfc.xref.RFC2817.2">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.3">A</a><ul class="ind"> 2829 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.RFC2817.2">10.2</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A</a></li> 2866 2830 </ul> 2867 2831 </li> … … 2888 2852 <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind"> 2889 2853 <li class="indline1">Safe Methods <a class="iref" href="#rfc.iref.s.1"><b>7.1.1</b></a></li> 2890 <li class="indline1">Server header <a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.s.43"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A .2</a></li>2854 <li class="indline1">Server header <a class="iref" href="#rfc.xref.header.server.1">5</a>, <a class="iref" href="#rfc.iref.s.43"><b>9.8</b></a>, <a class="iref" href="#rfc.xref.header.server.2">10.3</a>, <a class="iref" href="#rfc.xref.header.server.3">11.1</a>, <a class="iref" href="#rfc.xref.header.server.4">A</a></li> 2891 2855 <li class="indline1">Status Codes 2892 2856 <ul class="ind"> … … 2894 2858 <li class="indline1">101 Switching Protocols <a class="iref" href="#rfc.xref.status.101.1">4</a>, <a class="iref" href="#rfc.iref.s.3"><b>8.1.2</b></a>, <a class="iref" href="#rfc.xref.status.101.2">10.2</a></li> 2895 2859 <li class="indline1">200 OK <a class="iref" href="#rfc.xref.status.200.1">4</a>, <a class="iref" href="#rfc.iref.s.4"><b>8.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">10.2</a></li> 2896 <li class="indline1">201 Created <a class="iref" href="#rfc.xref.status.201.1">4</a>, <a class="iref" href="#rfc.iref.s.5"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">10.2</a> , <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>2860 <li class="indline1">201 Created <a class="iref" href="#rfc.xref.status.201.1">4</a>, <a class="iref" href="#rfc.iref.s.5"><b>8.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">10.2</a></li> 2897 2861 <li class="indline1">202 Accepted <a class="iref" href="#rfc.xref.status.202.1">4</a>, <a class="iref" href="#rfc.iref.s.6"><b>8.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">10.2</a></li> 2898 2862 <li class="indline1">203 Non-Authoritative Information <a class="iref" href="#rfc.xref.status.203.1">4</a>, <a class="iref" href="#rfc.iref.s.7"><b>8.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">10.2</a></li> … … 2901 2865 <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.10"><b>8.2.7</b></a></li> 2902 2866 <li class="indline1">300 Multiple Choices <a class="iref" href="#rfc.xref.status.300.1">4</a>, <a class="iref" href="#rfc.iref.s.11"><b>8.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">10.2</a></li> 2903 <li class="indline1">301 Moved Permanently <a class="iref" href="#rfc.xref.status.301.1">4</a>, <a class="iref" href="#rfc.iref.s.12"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">10.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A .2</a></li>2904 <li class="indline1">302 Found <a class="iref" href="#rfc.xref.status.302.1">4</a>, <a class="iref" href="#rfc.iref.s.13"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">10.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A .2</a></li>2905 <li class="indline1">303 See Other <a class="iref" href="#rfc.xref.status.303.1">4</a>, <a class="iref" href="#rfc.xref.status.303.2">8.3.3</a>, <a class="iref" href="#rfc.iref.s.14"><b>8.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.3">10.2</a> , <a class="iref" href="#rfc.xref.status.303.4">A.1</a></li>2867 <li class="indline1">301 Moved Permanently <a class="iref" href="#rfc.xref.status.301.1">4</a>, <a class="iref" href="#rfc.iref.s.12"><b>8.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">10.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A</a></li> 2868 <li class="indline1">302 Found <a class="iref" href="#rfc.xref.status.302.1">4</a>, <a class="iref" href="#rfc.iref.s.13"><b>8.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">10.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A</a></li> 2869 <li class="indline1">303 See Other <a class="iref" href="#rfc.xref.status.303.1">4</a>, <a class="iref" href="#rfc.xref.status.303.2">8.3.3</a>, <a class="iref" href="#rfc.iref.s.14"><b>8.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.3">10.2</a></li> 2906 2870 <li class="indline1">304 Not Modified <a class="iref" href="#rfc.iref.s.15"><b>8.3.5</b></a></li> 2907 <li class="indline1">305 Use Proxy <a class="iref" href="#rfc.xref.status.305.1">4</a>, <a class="iref" href="#rfc.iref.s.16"><b>8.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">10.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A .2</a></li>2871 <li class="indline1">305 Use Proxy <a class="iref" href="#rfc.xref.status.305.1">4</a>, <a class="iref" href="#rfc.iref.s.16"><b>8.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">10.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A</a></li> 2908 2872 <li class="indline1">306 (Unused) <a class="iref" href="#rfc.iref.s.17"><b>8.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">10.2</a></li> 2909 <li class="indline1">307 Temporary Redirect <a class="iref" href="#rfc.xref.status.307.1">4</a>, <a class="iref" href="#rfc.xref.status.307.2">8.3.3</a>, <a class="iref" href="#rfc.iref.s.18"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.3">10.2</a>, <a class="iref" href="#rfc.xref.status.307.4">A .1</a>, <a class="iref" href="#rfc.xref.status.307.5">A.2</a></li>2873 <li class="indline1">307 Temporary Redirect <a class="iref" href="#rfc.xref.status.307.1">4</a>, <a class="iref" href="#rfc.xref.status.307.2">8.3.3</a>, <a class="iref" href="#rfc.iref.s.18"><b>8.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.3">10.2</a>, <a class="iref" href="#rfc.xref.status.307.4">A</a></li> 2910 2874 <li class="indline1">400 Bad Request <a class="iref" href="#rfc.xref.status.400.1">4</a>, <a class="iref" href="#rfc.iref.s.19"><b>8.4.1</b></a>, <a class="iref" href="#rfc.xref.status.400.2">10.2</a></li> 2911 2875 <li class="indline1">401 Unauthorized <a class="iref" href="#rfc.iref.s.20"><b>8.4.2</b></a></li> 2912 2876 <li class="indline1">402 Payment Required <a class="iref" href="#rfc.xref.status.402.1">4</a>, <a class="iref" href="#rfc.iref.s.21"><b>8.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">10.2</a></li> 2913 <li class="indline1">403 Forbidden <a class="iref" href="#rfc.xref.status.403.1">4</a>, <a class="iref" href="#rfc.iref.s.22"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">10.2</a> , <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>2914 <li class="indline1">404 Not Found <a class="iref" href="#rfc.xref.status.404.1">4</a>, <a class="iref" href="#rfc.iref.s.23"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">10.2</a> , <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>2877 <li class="indline1">403 Forbidden <a class="iref" href="#rfc.xref.status.403.1">4</a>, <a class="iref" href="#rfc.iref.s.22"><b>8.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">10.2</a></li> 2878 <li class="indline1">404 Not Found <a class="iref" href="#rfc.xref.status.404.1">4</a>, <a class="iref" href="#rfc.iref.s.23"><b>8.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">10.2</a></li> 2915 2879 <li class="indline1">405 Method Not Allowed <a class="iref" href="#rfc.xref.status.405.1">4</a>, <a class="iref" href="#rfc.iref.s.24"><b>8.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">10.2</a></li> 2916 2880 <li class="indline1">406 Not Acceptable <a class="iref" href="#rfc.xref.status.406.1">4</a>, <a class="iref" href="#rfc.iref.s.25"><b>8.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">10.2</a></li> … … 2918 2882 <li class="indline1">408 Request Timeout <a class="iref" href="#rfc.xref.status.408.1">4</a>, <a class="iref" href="#rfc.iref.s.27"><b>8.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">10.2</a></li> 2919 2883 <li class="indline1">409 Conflict <a class="iref" href="#rfc.xref.status.409.1">4</a>, <a class="iref" href="#rfc.iref.s.28"><b>8.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">10.2</a></li> 2920 <li class="indline1">410 Gone <a class="iref" href="#rfc.xref.status.410.1">4</a>, <a class="iref" href="#rfc.iref.s.29"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">10.2</a> , <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>2884 <li class="indline1">410 Gone <a class="iref" href="#rfc.xref.status.410.1">4</a>, <a class="iref" href="#rfc.iref.s.29"><b>8.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">10.2</a></li> 2921 2885 <li class="indline1">411 Length Required <a class="iref" href="#rfc.xref.status.411.1">4</a>, <a class="iref" href="#rfc.iref.s.30"><b>8.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">10.2</a></li> 2922 2886 <li class="indline1">412 Precondition Failed <a class="iref" href="#rfc.iref.s.31"><b>8.4.13</b></a></li> … … 2930 2894 <li class="indline1">502 Bad Gateway <a class="iref" href="#rfc.xref.status.502.1">4</a>, <a class="iref" href="#rfc.iref.s.39"><b>8.5.3</b></a>, <a class="iref" href="#rfc.xref.status.502.2">10.2</a></li> 2931 2895 <li class="indline1">503 Service Unavailable <a class="iref" href="#rfc.xref.status.503.1">4</a>, <a class="iref" href="#rfc.iref.s.40"><b>8.5.4</b></a>, <a class="iref" href="#rfc.xref.status.503.2">10.2</a></li> 2932 <li class="indline1">504 Gateway Timeout <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.s.41"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a> , <a class="iref" href="#rfc.xref.status.504.3">A.1</a></li>2896 <li class="indline1">504 Gateway Timeout <a class="iref" href="#rfc.xref.status.504.1">4</a>, <a class="iref" href="#rfc.iref.s.41"><b>8.5.5</b></a>, <a class="iref" href="#rfc.xref.status.504.2">10.2</a></li> 2933 2897 <li class="indline1">505 HTTP Version Not Supported <a class="iref" href="#rfc.xref.status.505.1">4</a>, <a class="iref" href="#rfc.iref.s.42"><b>8.5.6</b></a>, <a class="iref" href="#rfc.xref.status.505.2">10.2</a></li> 2934 2898 </ul> … … 2941 2905 </li> 2942 2906 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind"> 2943 <li class="indline1">UNLINK method <a class="iref" href="#rfc.iref.u.2"><b>A.1</b></a></li>2944 2907 <li class="indline1">User-Agent header <a class="iref" href="#rfc.xref.header.user-agent.1">3</a>, <a class="iref" href="#rfc.iref.u.1"><b>9.9</b></a>, <a class="iref" href="#rfc.xref.header.user-agent.2">10.3</a>, <a class="iref" href="#rfc.xref.header.user-agent.3">11.1</a></li> 2945 2908 </ul> -
draft-ietf-httpbis/latest/p3-payload.html
r882 r912 386 386 <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A"> 387 387 <link rel="Appendix" title="B Additional Features" href="#rfc.section.B"> 388 <link rel="Appendix" title="C C ompatibility with Previous Versions" href="#rfc.section.C">388 <link rel="Appendix" title="C Changes from RFC 2616" href="#rfc.section.C"> 389 389 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 390 390 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> … … 401 401 <meta name="dct.creator" content="Reschke, J. F."> 402 402 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 403 <meta name="dct.issued" scheme="ISO8601" content="2010-07-2 3">403 <meta name="dct.issued" scheme="ISO8601" content="2010-07-24"> 404 404 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 405 405 <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 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 427 427 </tr> 428 428 <tr> 429 <td class="left">Expires: January 2 4, 2011</td>429 <td class="left">Expires: January 25, 2011</td> 430 430 <td class="right">J. Mogul</td> 431 431 </tr> … … 484 484 <tr> 485 485 <td class="left"></td> 486 <td class="right">July 2 3, 2010</td>486 <td class="right">July 24, 2010</td> 487 487 </tr> 488 488 </tbody> … … 510 510 in progress”. 511 511 </p> 512 <p>This Internet-Draft will expire in January 2 4, 2011.</p>512 <p>This Internet-Draft will expire in January 25, 2011.</p> 513 513 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 514 514 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 611 611 </ul> 612 612 </li> 613 <li class="tocline0">C. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 614 <li class="tocline1">C.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 615 <li class="tocline1">C.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 616 </ul> 617 </li> 613 <li class="tocline0">C. <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 618 614 <li class="tocline0">D. <a href="#collected.abnf">Collected ABNF</a></li> 619 615 <li class="tocline0">E. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> … … 636 632 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> 637 633 <p id="rfc.section.1.p.1">This document defines HTTP/1.1 message payloads (a.k.a., content), the associated metadata header fields that define how the 638 payload is intended to be interpreted by a recipient, the request header fields that m ayinfluence content selection, and634 payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, and 639 635 the various selection algorithms that are collectively referred to as HTTP content negotiation. 640 636 </p> … … 708 704 <p id="rfc.section.2.1.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence 709 705 of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that 710 not all characters m ay be available in a given character set and a character set may provide more than one sequence of octets711 to represent a particular character. This definition is intended to allow various kinds of character encoding, from simple712 si ngle-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques. However,713 the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information706 not all characters might be available in a given character set and a character set might provide more than one sequence of 707 octets to represent a particular character. This definition is intended to allow various kinds of character encoding, from 708 simple single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques. 709 However, the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information 714 710 to determine the exact mapping is not permitted. 715 711 </p> … … 730 726 <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header (in which the charset value is an unquoted token) 731 727 and as the value of a parameter in a Content-Type header (within a request or response), in which case the parameter value 732 of the charset parameter maybe quoted.728 of the charset parameter can be quoted. 733 729 </p> 734 730 <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a> <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>. … … 809 805 of a media-type, depending on its definition within the media type registry. 810 806 </p> 811 <p id="rfc.section.2.3.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production maybe transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.807 <p id="rfc.section.2.3.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent. 812 808 </p> 813 809 <p id="rfc.section.2.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications, … … 910 906 the specified type. 911 907 </p> 912 <p id="rfc.section.3.2.1.p.6">Clients that do so risk drawing incorrect conclusions, which m ayexpose additional security risks (e.g., "privilege escalation").908 <p id="rfc.section.3.2.1.p.6">Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege escalation"). 913 909 Implementers are encouraged to provide a means of disabling such "content sniffing" when it is used. 914 910 </p> 915 <p id="rfc.section.3.2.1.p.7">Content-Encoding may be used to indicate any additional content codings applied to the data, usually for the purpose of data916 compression,that are a property of the representation. There is no default encoding.911 <p id="rfc.section.3.2.1.p.7">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression, 912 that are a property of the representation. There is no default encoding. 917 913 </p> 918 914 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 934 930 <p id="rfc.section.4.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number 935 931 of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by 936 a user-agent), server-driven negotiation becomes unwieldy, and m aynot be appropriate. Conversely, when the number of representations937 to choose from is very large, agent-driven negotiation m aynot be appropriate.932 a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations 933 to choose from is very large, agent-driven negotiation might not be appropriate. 938 934 </p> 939 935 <p id="rfc.section.4.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might … … 961 957 </li> 962 958 <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li> 963 <li>It m aylimit a public cache's ability to use the same response for multiple user's requests.</li>959 <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li> 964 960 </ol> 965 961 <p id="rfc.section.4.1.p.4">HTTP/1.1 includes the following request-header fields for enabling server-driven negotiation through description of user agent … … 977 973 an initial response from the origin server. Selection is based on a list of the available representations of the response 978 974 included within the header fields or body of the initial response, with each representation identified by its own URI. Selection 979 from among the representations maybe performed automatically (if the user agent is capable of doing so) or manually by the975 from among the representations can be performed automatically (if the user agent is capable of doing so) or manually by the 980 976 user selecting from a generated (possibly hypertext) menu. 981 977 </p> … … 1285 1281 and the representation selected for this response can also be found at the identified URI. For other methods, such a Content-Location 1286 1282 indicates that this representation contains a report on the action's status and the same report is available (for future access 1287 with GET) at the given URI. For example, a purchase transaction made via the POST method m ay include a receipt document as1288 the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt1283 with GET) at the given URI. For example, a purchase transaction made via the POST method might include a receipt document 1284 as the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt 1289 1285 in the future. 1290 1286 </p> … … 1563 1559 <tr> 1564 1560 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1565 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC 1950 is an Informational RFC, thus it m aybe less stable than this specification. On the other hand, this downward reference1561 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 1566 1562 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1567 1563 </td> … … 1569 1565 <tr> 1570 1566 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1571 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it m aybe less stable than this specification. On the other hand, this downward reference1567 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 1572 1568 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1573 1569 </td> … … 1575 1571 <tr> 1576 1572 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1577 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it m aybe less stable than this specification. On the other hand, this downward reference1573 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference 1578 1574 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1579 1575 </td> … … 1806 1802 <p id="rfc.section.B.1.p.7">See <a href="#content-disposition.issues" title="Content-Disposition Issues">Section 7.2</a> for Content-Disposition security issues. 1807 1803 </p> 1808 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 1809 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 1810 <p id="rfc.section.C.1.p.1">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 5.2</a>) 1811 </p> 1812 <p id="rfc.section.C.1.p.2">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce 1813 it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.3"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. 1814 </p> 1815 <p id="rfc.section.C.1.p.3">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section 2.2</a>) 1816 </p> 1817 <p id="rfc.section.C.1.p.4">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.13"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.2"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.14"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1818 </p> 1819 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1820 <p id="rfc.section.C.2.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section 2.1</a>) 1821 </p> 1822 <p id="rfc.section.C.2.p.2">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken 1804 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1805 <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section 2.1</a>) 1806 </p> 1807 <p id="rfc.section.C.p.2">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken 1823 1808 servers emitting bogus Content-Location headers, and also the potentially undesirable effect of potentially breaking relative 1824 1809 links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section 5.7</a>) 1825 1810 </p> 1826 <p id="rfc.section.C. 2.p.3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A.5</a>)1811 <p id="rfc.section.C.p.3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A.5</a>) 1827 1812 </p> 1828 1813 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 2090 2075 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/183">http://tools.ietf.org/wg/httpbis/trac/ticket/183</a>>: "'requested resource' in content-encoding definition" 2091 2076 </li> 2077 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" 2078 </li> 2092 2079 </ul> 2093 2080 <p id="rfc.section.E.12.p.2">Partly resolved issues: </p> … … 2097 2084 </ul> 2098 2085 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2099 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index. L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>2086 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> 2100 2087 </p> 2101 2088 <div class="print2col"> … … 2103 2090 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 2104 2091 <li class="indline1">Accept header <a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">4.1</a>, <a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept.3">6.1</a></li> 2105 <li class="indline1">Accept-Charset header <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.a.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">6.1</a> , <a class="iref" href="#rfc.xref.header.accept-charset.3">C.1</a></li>2092 <li class="indline1">Accept-Charset header <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.a.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">6.1</a></li> 2106 2093 <li class="indline1">Accept-Encoding header <a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.accept-encoding.3">6.1</a></li> 2107 2094 <li class="indline1">Accept-Language header <a class="iref" href="#rfc.xref.header.accept-language.1">4.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.accept-language.2">6.1</a></li> 2108 <li class="indline1">Alternates header <a class="iref" href="#rfc.iref.a.5"><b>C.1</b></a></li>2109 2095 </ul> 2110 2096 </li> … … 2124 2110 <li class="indline1">compress (Coding Format) <a class="iref" href="#rfc.iref.c.2">2.2</a></li> 2125 2111 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.1">1.1</a></li> 2126 <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.14"><b>C.1</b></a></li>2127 2112 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c.12"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li> 2128 2113 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 2129 2114 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.8"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 2130 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.9"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C .2</a></li>2115 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.9"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C</a></li> 2131 2116 <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.10"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 2132 2117 <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.11"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> 2133 <li class="indline1">Content-Version header <a class="iref" href="#rfc.iref.c.13"><b>C.1</b></a></li>2134 2118 </ul> 2135 2119 </li> 2136 2120 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind"> 2137 2121 <li class="indline1">deflate (Coding Format) <a class="iref" href="#rfc.iref.d.1">2.2</a></li> 2138 <li class="indline1">Derived-From header <a class="iref" href="#rfc.iref.d.2"><b>C.1</b></a></li>2139 2122 </ul> 2140 2123 </li> … … 2194 2177 <ul class="ind"> 2195 2178 <li class="indline1">Accept <a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">4.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept.3">6.1</a></li> 2196 <li class="indline1">Accept-Charset <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">6.1</a> , <a class="iref" href="#rfc.xref.header.accept-charset.3">C.1</a></li>2179 <li class="indline1">Accept-Charset <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">6.1</a></li> 2197 2180 <li class="indline1">Accept-Encoding <a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.accept-encoding.3">6.1</a></li> 2198 2181 <li class="indline1">Accept-Language <a class="iref" href="#rfc.xref.header.accept-language.1">4.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.accept-language.2">6.1</a></li> 2199 <li class="indline1">Alternate <a class="iref" href="#rfc.iref.h.12"><b>C.1</b></a></li>2200 <li class="indline1">Content-Base <a class="iref" href="#rfc.iref.h.18"><b>C.1</b></a></li>2201 2182 <li class="indline1">Content-Disposition <a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.h.11"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li> 2202 2183 <li class="indline1">Content-Encoding <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 2203 2184 <li class="indline1">Content-Language <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 2204 <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C .2</a></li>2185 <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C</a></li> 2205 2186 <li class="indline1">Content-MD5 <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 2206 2187 <li class="indline1">Content-Type <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.h.9"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> 2207 <li class="indline1">Content-Version <a class="iref" href="#rfc.iref.h.13"><b>C.1</b></a></li>2208 <li class="indline1">Derived-From <a class="iref" href="#rfc.iref.h.14"><b>C.1</b></a></li>2209 <li class="indline1">Link <a class="iref" href="#rfc.iref.h.15"><b>C.1</b></a></li>2210 2188 <li class="indline1">MIME-Version <a class="iref" href="#rfc.xref.mime-version.1">6.1</a>, <a class="iref" href="#rfc.iref.h.10"><b>A.1</b></a></li> 2211 <li class="indline1">Public <a class="iref" href="#rfc.iref.h.17"><b>C.1</b></a></li>2212 <li class="indline1">URI <a class="iref" href="#rfc.iref.h.16"><b>C.1</b></a></li>2213 2189 </ul> 2214 2190 </li> … … 2218 2194 <li class="indline1">identity (Coding Format) <a class="iref" href="#rfc.iref.i.1">2.2</a></li> 2219 2195 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a></li> 2220 </ul>2221 </li>2222 <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind">2223 <li class="indline1">Link header <a class="iref" href="#rfc.iref.l.1"><b>C.1</b></a></li>2224 2196 </ul> 2225 2197 </li> … … 2265 2237 </li> 2266 2238 <li class="indline1">payload <a class="iref" href="#rfc.iref.p.1">1.1</a></li> 2267 <li class="indline1">Public header <a class="iref" href="#rfc.iref.p.2"><b>C.1</b></a></li>2268 2239 </ul> 2269 2240 </li> … … 2285 2256 </ul> 2286 2257 </li> 2287 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">9.1</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a><ul class="ind"> 2288 <li class="indline1"><em>Section 19.6.2</em> <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a></li> 2289 </ul> 2290 </li> 2258 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">9.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">9.1</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a></li> 2291 2259 <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li> 2292 2260 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li> … … 2298 2266 <li class="indline1"><em>RFC2295</em> <a class="iref" href="#rfc.xref.RFC2295.1">4</a>, <a class="iref" href="#RFC2295"><b>9.2</b></a></li> 2299 2267 <li class="indline1"><em>RFC2388</em> <a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>9.2</b></a></li> 2300 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#rfc.xref.RFC2557.1">5.7</a>, <a class="iref" href="#RFC2557"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.2">A.7</a> , <a class="iref" href="#rfc.xref.RFC2557.3">C.1</a><ul class="ind">2268 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#rfc.xref.RFC2557.1">5.7</a>, <a class="iref" href="#RFC2557"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.2">A.7</a><ul class="ind"> 2301 2269 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.RFC2557.1">5.7</a></li> 2302 2270 </ul> … … 2331 2299 </ul> 2332 2300 </li> 2333 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">2334 <li class="indline1">URI header <a class="iref" href="#rfc.iref.u.1"><b>C.1</b></a></li>2335 </ul>2336 </li>2337 2301 </ul> 2338 2302 </div> -
draft-ietf-httpbis/latest/p4-conditional.html
r879 r912 385 385 <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9"> 386 386 <link rel="Chapter" href="#rfc.section.10" title="10 References"> 387 <link rel="Appendix" title="A C ompatibility with Previous Versions" href="#rfc.section.A">387 <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A"> 388 388 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 389 389 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> … … 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-07-2 3">402 <meta name="dct.issued" scheme="ISO8601" content="2010-07-24"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <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 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: January 2 4, 2011</td>428 <td class="left">Expires: January 25, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">July 2 3, 2010</td>485 <td class="right">July 24, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire in January 2 4, 2011.</p>511 <p>This Internet-Draft will expire in January 25, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 569 569 </li> 570 570 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> 571 <li class="tocline0">A. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 572 <li class="tocline1">A.1 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 573 </ul> 574 </li> 571 <li class="tocline0">A. <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 575 572 <li class="tocline0">B. <a href="#collected.abnf">Collected ABNF</a></li> 576 573 <li class="tocline0">C. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> … … 652 649 Accept-Encoding: gzip 653 650 654 </pre><p id="rfc.section.2.1.p.3">In this case, the response m ay or maynot use the gzip content coding. If it does not, the response might look like:</p>651 </pre><p id="rfc.section.2.1.p.3">In this case, the response might or might not use the gzip content coding. If it does not, the response might look like:</p> 655 652 <div id="rfc.figure.u.5"></div> 656 653 <p>>> Response:</p><pre class="text">HTTP/1.1 200 OK … … 1073 1070 <div id="rfc.figure.u.18"></div><pre class="text"> Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT 1074 1071 </pre><p id="rfc.section.6.6.p.5">The exact meaning of this header field depends on the implementation of the origin server and the nature of the original resource. 1075 For files, it m ay be just the file system last-modified time. For representations with dynamically included parts, it may1076 be the most recent of the set of last-modify times for its component parts. For database gateways, it m aybe the last-update1077 time stamp of the record. For virtual objects, it m aybe the last time the internal state changed.1072 For files, it might be just the file system last-modified time. For representations with dynamically included parts, it might 1073 be the most recent of the set of last-modify times for its component parts. For database gateways, it might be the last-update 1074 time stamp of the record. For virtual objects, it might be the last time the internal state changed. 1078 1075 </p> 1079 1076 <p id="rfc.section.6.6.p.6">An origin server <em class="bcp14">MUST NOT</em> send a Last-Modified date which is later than the server's time of message origination. In such cases, where the resource's … … 1252 1249 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 1253 1250 </div> 1254 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 1255 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1256 <p id="rfc.section.A.1.p.1">Allow weak entity-tags in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak and Strong Validators">4</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.3" title="If-None-Match">6.4</a>). 1251 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1252 <p id="rfc.section.A.p.1">Allow weak entity-tags in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak and Strong Validators">4</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.3" title="If-None-Match">6.4</a>). 1257 1253 </p> 1258 1254 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 1375 1371 </li> 1376 1372 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>>: "Clarify entity / representation / variant terminology" 1373 </li> 1374 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" 1377 1375 </li> 1378 1376 </ul> … … 1422 1420 <li class="indline1">If-Match <a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.if-match.2">7.2</a></li> 1423 1421 <li class="indline1">If-Modified-Since <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-modified-since.1">7.2</a></li> 1424 <li class="indline1">If-None-Match <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">7.2</a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">A .1</a></li>1422 <li class="indline1">If-None-Match <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">7.2</a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">A</a></li> 1425 1423 <li class="indline1">If-Unmodified-Since <a class="iref" href="#rfc.iref.h.5"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.if-unmodified-since.1">7.2</a></li> 1426 1424 <li class="indline1">Last-Modified <a class="iref" href="#rfc.iref.h.6"><b>6.6</b></a>, <a class="iref" href="#rfc.xref.header.last-modified.1">7.2</a></li> … … 1432 1430 <li class="indline1">If-Match header <a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.if-match.2">7.2</a></li> 1433 1431 <li class="indline1">If-Modified-Since header <a class="iref" href="#rfc.iref.i.2"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.if-modified-since.1">7.2</a></li> 1434 <li class="indline1">If-None-Match header <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.iref.i.3"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">7.2</a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">A .1</a></li>1432 <li class="indline1">If-None-Match header <a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.iref.i.3"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">7.2</a>, <a class="iref" href="#rfc.xref.header.if-none-match.3">A</a></li> 1435 1433 <li class="indline1">If-Unmodified-Since header <a class="iref" href="#rfc.iref.i.4"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.if-unmodified-since.1">7.2</a></li> 1436 1434 </ul> -
draft-ietf-httpbis/latest/p5-range.html
r876 r912 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-07-2 3">402 <meta name="dct.issued" scheme="ISO8601" content="2010-07-24"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <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 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: January 2 4, 2011</td>428 <td class="left">Expires: January 25, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">July 2 3, 2010</td>485 <td class="right">July 24, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire in January 2 4, 2011.</p>511 <p>This Internet-Draft will expire in January 25, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 569 569 <li class="tocline0">A. <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> 570 570 <li class="tocline0">B. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 571 <li class="tocline1">B.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 572 <li class="tocline1">B.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 571 <li class="tocline1">B.1 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 573 572 </ul> 574 573 </li> … … 774 773 </pre><p id="rfc.section.5.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping 775 774 ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" 776 as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix B.1</a> for a compatibility issue.775 as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. 777 776 </p> 778 777 <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request. … … 1141 1140 </pre> <p id="rfc.section.A.p.7">Notes: </p> 1142 1141 <ol> 1143 <li>Additional CRLFs may precede the first boundary string in the body.</li> 1142 <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body. 1143 </li> 1144 1144 <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly. 1145 1145 </li> … … 1148 1148 </ol> 1149 1149 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 1150 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 1151 <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1152 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1153 computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section 5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) 1154 </p> 1155 <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving 1156 a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length 1157 of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section 5.2</a>) 1158 </p> 1159 <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send 1160 needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.5" title="If-Range">5.3</a>) 1161 </p> 1162 <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document. 1163 The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside 1164 of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.3" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">5.2</a>) 1165 </p> 1166 <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1167 <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.3" title="206 Partial Content">Section 3.1</a>) 1168 </p> 1169 <p id="rfc.section.B.2.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) 1150 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 1151 <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section 3.1</a>) 1152 </p> 1153 <p id="rfc.section.B.1.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) 1170 1154 </p> 1171 1155 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 1319 1303 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>>: "Clarify entity / representation / variant terminology" 1320 1304 </li> 1305 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "Clarify entity / representation / variant terminology" 1306 </li> 1307 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" 1308 </li> 1321 1309 </ul> 1322 1310 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 1326 1314 <ul class="ind"> 1327 1315 <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind"> 1328 <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">6.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.1</a> , <a class="iref" href="#rfc.xref.status.206.3">B.2</a></li>1316 <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">6.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.1</a></li> 1329 1317 </ul> 1330 1318 </li> 1331 1319 <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind"> 1332 <li class="indline1">416 Requested Range Not Satisfiable (status code) <a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">6.1</a> , <a class="iref" href="#rfc.xref.status.416.3">B.1</a></li>1320 <li class="indline1">416 Requested Range Not Satisfiable (status code) <a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">6.1</a></li> 1333 1321 </ul> 1334 1322 </li> … … 1338 1326 </li> 1339 1327 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 1340 <li class="indline1">Content-Range header <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.2</a> , <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>1328 <li class="indline1">Content-Range header <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.2</a></li> 1341 1329 </ul> 1342 1330 </li> … … 1375 1363 <ul class="ind"> 1376 1364 <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.2</a></li> 1377 <li class="indline1">Content-Range <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.2</a> , <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>1378 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a> , <a class="iref" href="#rfc.xref.header.if-range.5">B.1</a></li>1365 <li class="indline1">Content-Range <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.2</a></li> 1366 <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a></li> 1379 1367 <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.2</a></li> 1380 1368 </ul> … … 1383 1371 </li> 1384 1372 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1385 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a> , <a class="iref" href="#rfc.xref.header.if-range.5">B.1</a></li>1373 <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a></li> 1386 1374 </ul> 1387 1375 </li> … … 1398 1386 </li> 1399 1387 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1400 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.6">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a> , <a class="iref" href="#rfc.xref.Part1.7">B.1</a><ul class="ind">1388 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.6">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a><ul class="ind"> 1401 1389 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1402 1390 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li> … … 1430 1418 <li class="indline1">Status Codes 1431 1419 <ul class="ind"> 1432 <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">6.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.1</a> , <a class="iref" href="#rfc.xref.status.206.3">B.2</a></li>1433 <li class="indline1">416 Requested Range Not Satisfiable <a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">6.1</a> , <a class="iref" href="#rfc.xref.status.416.3">B.1</a></li>1420 <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">6.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.1</a></li> 1421 <li class="indline1">416 Requested Range Not Satisfiable <a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">6.1</a></li> 1434 1422 </ul> 1435 1423 </li> -
draft-ietf-httpbis/latest/p6-cache.html
r900 r912 386 386 <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7"> 387 387 <link rel="Chapter" href="#rfc.section.8" title="8 References"> 388 <link rel="Appendix" title="A C ompatibility with Previous Versions" href="#rfc.section.A">388 <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A"> 389 389 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 390 390 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> … … 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-07-2 3">404 <meta name="dct.issued" scheme="ISO8601" content="2010-07-24"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: January 2 4, 2011</td>430 <td class="left">Expires: January 25, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">July 2 3, 2010</td>491 <td class="right">July 24, 2010</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire in January 2 4, 2011.</p>517 <p>This Internet-Draft will expire in January 25, 2011.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 594 594 </li> 595 595 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> 596 <li class="tocline0">A. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 597 <li class="tocline1">A.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 598 <li class="tocline1">A.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 599 </ul> 600 </li> 596 <li class="tocline0">A. <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 601 597 <li class="tocline0">B. <a href="#collected.abnf">Collected ABNF</a></li> 602 598 <li class="tocline0">C. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> … … 625 621 <p id="rfc.section.1.1.p.1">An HTTP <dfn>cache</dfn> is a local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. A cache 626 622 stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests. 627 Any client or server may includea cache, though a cache cannot be used by a server that is acting as a tunnel.623 Any client or server <em class="bcp14">MAY</em> employ a cache, though a cache cannot be used by a server that is acting as a tunnel. 628 624 </p> 629 625 <p id="rfc.section.1.1.p.2">Caching would be useless if it did not significantly improve performance. The goal of caching in HTTP/1.1 is to reuse a prior … … 638 634 <ul class="empty"> 639 635 <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 640 Even when a response is cacheable, there m aybe additional constraints on whether a cache can use the cached copy to satisfy636 Even when a response is cacheable, there might be additional constraints on whether a cache can use the cached copy to satisfy 641 637 a particular request. 642 638 </li> … … 803 799 </p> 804 800 <p id="rfc.section.2.3.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past. 805 This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment" id="TODO-response-stale">[<a href="#TODO-response-stale" class="smpl">TODO-response-stale</a>: This wording may cause confusion, because the response may still be served stale.]</span> 806 </p> 807 <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, HTTP caches may also assign heuristic expiration times 808 when they are not specified, employing algorithms that use other header values (such as the Last-Modified time) to estimate 809 a plausible expiration time. The HTTP/1.1 specification does not provide specific algorithms, but does impose worst-case constraints 810 on their results. 801 This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment" id="TODO-response-stale">[<a href="#TODO-response-stale" class="smpl">TODO-response-stale</a>: This wording might cause confusion, because the response might still be served stale.]</span> 802 </p> 803 <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, HTTP caches <em class="bcp14">MAY</em> assign heuristic expiration times when explicit times are not specified, employing algorithms that use other header values 804 (such as the Last-Modified time) to estimate a plausible expiration time. The HTTP/1.1 specification does not provide specific 805 algorithms, but does impose worst-case constraints on their results. 811 806 </p> 812 807 <div id="rfc.figure.u.3"></div> … … 814 809 </pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. 815 810 </p> 816 <p id="rfc.section.2.3.p.7">Additionally, clients m ayneed to influence freshness calculation. They can do this using several request cache directives,811 <p id="rfc.section.2.3.p.7">Additionally, clients might need to influence freshness calculation. They can do this using several request cache directives, 817 812 with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>. 818 813 </p> … … 989 984 </li> 990 985 </ul> 991 <p id="rfc.section.2.7.p.3">If (after any normali sation that maytake place) a header field is absent from a request, it can only match another request986 <p id="rfc.section.2.7.p.3">If (after any normalization that might take place) a header field is absent from a request, it can only match another request 992 987 if it is also absent there. 993 988 </p> … … 1003 998 be used to satisfy the request. 1004 999 </p> 1005 <p id="rfc.section.2.8.p.2">If the new response contains an ETag, it identifies the stored response to use. <span class="comment" id="TODO-mention-CL">[<a href="#TODO-mention-CL" class="smpl">TODO-mention-CL</a>: m ayneed language about Content-Location here]</span><span class="comment" id="TODO-inm-mult-etags">[<a href="#TODO-inm-mult-etags" class="smpl">TODO-inm-mult-etags</a>: cover case where INM with multiple etags was sent]</span>1000 <p id="rfc.section.2.8.p.2">If the new response contains an ETag, it identifies the stored response to use. <span class="comment" id="TODO-mention-CL">[<a href="#TODO-mention-CL" class="smpl">TODO-mention-CL</a>: might need language about Content-Location here]</span><span class="comment" id="TODO-inm-mult-etags">[<a href="#TODO-inm-mult-etags" class="smpl">TODO-inm-mult-etags</a>: cover case where INM with multiple etags was sent]</span> 1006 1001 </p> 1007 1002 <p id="rfc.section.2.8.p.3">If the status code is 206 (partial content), both the stored and new responses <em class="bcp14">MUST</em> have validators, and those validators <em class="bcp14">MUST</em> match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). Otherwise, the responses <em class="bcp14">MUST NOT</em> be combined. … … 1041 1036 </p> 1042 1037 <p id="rfc.section.3.1.p.6">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not 1043 true, since HTTP/1.0 caches m aynot implement the Age header field.1038 true, since HTTP/1.0 caches might not implement the Age header field. 1044 1039 </p> 1045 1040 <div id="rfc.iref.c.3"></div> … … 1090 1085 </li> 1091 1086 <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches 1092 might not recognize or obey this directive, and communications networks m aybe vulnerable to eavesdropping.1087 might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping. 1093 1088 </li> 1094 1089 </ul> … … 1157 1152 with the listed response headers. That is, the specified field-names(s) <em class="bcp14">MUST NOT</em> be stored by a shared cache, whereas the remainder of the response message <em class="bcp14">MAY</em> be. 1158 1153 </li> 1159 <li> <b>Note:</b> This usage of the word private only controls where the response may be stored, andcannot ensure the privacy of the message1154 <li> <b>Note:</b> This usage of the word private only controls where the response can be stored; it cannot ensure the privacy of the message 1160 1155 content. Also, private response directives with field-names are often handled by implementations as if an unqualified private 1161 1156 directive was received; i.e., the special handling for the qualified form is not widely implemented. … … 1184 1179 </li> 1185 1180 <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches 1186 might not recognize or obey this directive, and communications networks m aybe vulnerable to eavesdropping.1181 might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping. 1187 1182 </li> 1188 1183 </ul> … … 1325 1320 <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the request-headers (e.g., the network address 1326 1321 of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this 1327 response is appropriate. The "*" value <em class="bcp14">MUST NOT</em> be generated by a proxy server ; it may only be generated by an origin server.1322 response is appropriate. The "*" value <em class="bcp14">MUST NOT</em> be generated by a proxy server. 1328 1323 </p> 1329 1324 <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard request-header fields defined by this specification. Field names … … 1681 1676 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 1682 1677 </div> 1683 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 1684 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> 1685 <p id="rfc.section.A.1.p.1">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.1</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.4" title="Cache-Control">3.2</a>). 1686 </p> 1687 <p id="rfc.section.A.1.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send 1688 needed headers in a 206 response, this problem can be avoided. (<a href="#combining.headers" title="Combining Responses">Section 2.8</a>) 1689 </p> 1690 <p id="rfc.section.A.1.p.3">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>) 1691 </p> 1692 <p id="rfc.section.A.1.p.4">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#expiration.model" title="Freshness Model">2.3</a>, <a href="#combining.headers" title="Combining Responses">2.8</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.5" title="Cache-Control">3.2</a>, and <a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests. 1693 </p> 1694 <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> 1695 <p id="rfc.section.A.2.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>) 1696 </p> 1697 <p id="rfc.section.A.2.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to 1678 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1679 <p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>) 1680 </p> 1681 <p id="rfc.section.A.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to 1698 1682 use. (<a href="#validation.model" title="Validation Model">Section 2.4</a>) 1699 1683 </p> 1700 <p id="rfc.section.A. 2.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a>)1701 </p> 1702 <p id="rfc.section.A. 2.p.4">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented.1703 (<a href="#header.warning" id="rfc.xref.header.warning. 5" title="Warning">Section 3.6</a>)1684 <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a>) 1685 </p> 1686 <p id="rfc.section.A.p.4">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented. 1687 (<a href="#header.warning" id="rfc.xref.header.warning.4" title="Warning">Section 3.6</a>) 1704 1688 </p> 1705 1689 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 1917 1901 </ul> 1918 1902 <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a> <a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p6-cache-10</a></h2> 1919 <p id="rfc.section.C.12.p.1">None yet.</p> 1903 <p id="rfc.section.C.12.p.1">Closed issues: </p> 1904 <ul> 1905 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" 1906 </li> 1907 </ul> 1920 1908 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1921 1909 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> … … 1946 1934 </ul> 1947 1935 </li> 1948 <li class="indline1">Cache-Control header <a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.2</a>, <a class="iref" href="#rfc.iref.c.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.3">5.2</a> , <a class="iref" href="#rfc.xref.header.cache-control.4">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">A.1</a></li>1936 <li class="indline1">Cache-Control header <a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.2</a>, <a class="iref" href="#rfc.iref.c.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.3">5.2</a></li> 1949 1937 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.2">1.2</a></li> 1950 1938 </ul> … … 1995 1983 <ul class="ind"> 1996 1984 <li class="indline1">Age <a class="iref" href="#rfc.xref.header.age.1">2.2</a>, <a class="iref" href="#rfc.xref.header.age.2">2.3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.header.age.3">5.2</a></li> 1997 <li class="indline1">Cache-Control <a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.3">5.2</a> , <a class="iref" href="#rfc.xref.header.cache-control.4">A.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.5">A.1</a></li>1985 <li class="indline1">Cache-Control <a class="iref" href="#rfc.xref.header.cache-control.1">2.1</a>, <a class="iref" href="#rfc.xref.header.cache-control.2">2.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.header.cache-control.3">5.2</a></li> 1998 1986 <li class="indline1">Expires <a class="iref" href="#rfc.xref.header.expires.1">2.1</a>, <a class="iref" href="#rfc.xref.header.expires.2">2.3</a>, <a class="iref" href="#rfc.xref.header.expires.3">2.3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>3.3</b></a>, <a class="iref" href="#rfc.xref.header.expires.4">5.2</a></li> 1999 1987 <li class="indline1">Pragma <a class="iref" href="#rfc.xref.header.pragma.1">2.2</a>, <a class="iref" href="#rfc.xref.header.pragma.2">3.2</a>, <a class="iref" href="#rfc.iref.h.5"><b>3.4</b></a>, <a class="iref" href="#rfc.xref.header.pragma.3">5.2</a></li> 2000 1988 <li class="indline1">Vary <a class="iref" href="#rfc.xref.header.vary.1">2.7</a>, <a class="iref" href="#rfc.iref.h.6"><b>3.5</b></a>, <a class="iref" href="#rfc.xref.header.vary.2">5.2</a></li> 2001 <li class="indline1">Warning <a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.8</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">A .1</a>, <a class="iref" href="#rfc.xref.header.warning.5">A.2</a></li>1989 <li class="indline1">Warning <a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.8</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">A</a></li> 2002 1990 </ul> 2003 1991 </li> … … 2139 2127 </li> 2140 2128 <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind"> 2141 <li class="indline1">Warning header <a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.8</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">A .1</a>, <a class="iref" href="#rfc.xref.header.warning.5">A.2</a></li>2129 <li class="indline1">Warning header <a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.8</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.2</a>, <a class="iref" href="#rfc.xref.header.warning.4">A</a></li> 2142 2130 </ul> 2143 2131 </li> -
draft-ietf-httpbis/latest/p7-auth.html
r878 r912 379 379 <link rel="Chapter" title="6 Acknowledgments" href="#rfc.section.6"> 380 380 <link rel="Chapter" href="#rfc.section.7" title="7 References"> 381 <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A"> 382 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 383 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 381 <link rel="Appendix" title="A Collected ABNF" href="#rfc.section.A"> 382 <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> 384 383 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.518, 2010-06-27 12:07:31, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 385 384 <link rel="schema.dct" href="http://purl.org/dc/terms/"> … … 394 393 <meta name="dct.creator" content="Reschke, J. F."> 395 394 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 396 <meta name="dct.issued" scheme="ISO8601" content="2010-07-2 3">395 <meta name="dct.issued" scheme="ISO8601" content="2010-07-24"> 397 396 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 398 397 <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 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 425 424 </tr> 426 425 <tr> 427 <td class="left">Expires: January 2 4, 2011</td>426 <td class="left">Expires: January 25, 2011</td> 428 427 <td class="right">HP</td> 429 428 </tr> … … 478 477 <tr> 479 478 <td class="left"></td> 480 <td class="right">July 2 3, 2010</td>479 <td class="right">July 24, 2010</td> 481 480 </tr> 482 481 </tbody> … … 493 492 list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. 494 493 </p> 495 <p>The changes in this draft are summarized in <a href="#changes.since.10" title="Since draft-ietf-httpbis-p7-auth-10">Appendix C.12</a>.494 <p>The changes in this draft are summarized in <a href="#changes.since.10" title="Since draft-ietf-httpbis-p7-auth-10">Appendix B.12</a>. 496 495 </p> 497 496 <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1> … … 504 503 in progress”. 505 504 </p> 506 <p>This Internet-Draft will expire in January 2 4, 2011.</p>505 <p>This Internet-Draft will expire in January 25, 2011.</p> 507 506 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 508 507 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 559 558 </li> 560 559 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> 561 <li class="tocline0">A. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> 562 <li class="tocline1">A.1 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 563 </ul> 564 </li> 565 <li class="tocline0">B. <a href="#collected.abnf">Collected ABNF</a></li> 566 <li class="tocline0">C. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 567 <li class="tocline1">C.1 <a href="#rfc.section.C.1">Since RFC2616</a></li> 568 <li class="tocline1">C.2 <a href="#rfc.section.C.2">Since draft-ietf-httpbis-p7-auth-00</a></li> 569 <li class="tocline1">C.3 <a href="#rfc.section.C.3">Since draft-ietf-httpbis-p7-auth-01</a></li> 570 <li class="tocline1">C.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li> 571 <li class="tocline1">C.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li> 572 <li class="tocline1">C.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li> 573 <li class="tocline1">C.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></li> 574 <li class="tocline1">C.8 <a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></li> 575 <li class="tocline1">C.9 <a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></li> 576 <li class="tocline1">C.10 <a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></li> 577 <li class="tocline1">C.11 <a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></li> 578 <li class="tocline1">C.12 <a href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></li> 560 <li class="tocline0">A. <a href="#collected.abnf">Collected ABNF</a></li> 561 <li class="tocline0">B. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> 562 <li class="tocline1">B.1 <a href="#rfc.section.B.1">Since RFC2616</a></li> 563 <li class="tocline1">B.2 <a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li> 564 <li class="tocline1">B.3 <a href="#rfc.section.B.3">Since draft-ietf-httpbis-p7-auth-01</a></li> 565 <li class="tocline1">B.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li> 566 <li class="tocline1">B.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li> 567 <li class="tocline1">B.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li> 568 <li class="tocline1">B.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></li> 569 <li class="tocline1">B.8 <a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></li> 570 <li class="tocline1">B.9 <a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></li> 571 <li class="tocline1">B.10 <a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></li> 572 <li class="tocline1">B.11 <a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></li> 573 <li class="tocline1">B.12 <a href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></li> 579 574 </ul> 580 575 </li> … … 600 595 </p> 601 596 <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="notation" href="#notation">Syntax Notation</a></h2> 602 <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix B</a> shows the collected ABNF, with the list rule expanded.597 <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix A</a> shows the collected ABNF, with the list rule expanded. 603 598 </p> 604 599 <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG … … 863 858 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 864 859 </div> 865 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> 866 <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 867 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 860 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 868 861 <div id="rfc.figure.u.7"></div> <pre class="inline"><a href="#header.authorization" class="smpl">Authorization</a> = "Authorization:" OWS Authorization-v 869 862 <a href="#header.authorization" class="smpl">Authorization-v</a> = credentials … … 889 882 ; Proxy-Authorization defined but not used 890 883 ; WWW-Authenticate defined but not used 891 </pre><h1 id="rfc.section. C"><a href="#rfc.section.C">C.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>892 <h2 id="rfc.section. C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616884 </pre><h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 885 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> Since RFC2616 893 886 </h2> 894 <p id="rfc.section. C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.895 </p> 896 <h2 id="rfc.section. C.2"><a href="#rfc.section.C.2">C.2</a> Since draft-ietf-httpbis-p7-auth-00887 <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 888 </p> 889 <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> Since draft-ietf-httpbis-p7-auth-00 897 890 </h2> 898 <p id="rfc.section. C.2.p.1">Closed issues: </p>891 <p id="rfc.section.B.2.p.1">Closed issues: </p> 899 892 <ul> 900 893 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>>: "Normative and Informative references" 901 894 </li> 902 895 </ul> 903 <h2 id="rfc.section. C.3"><a href="#rfc.section.C.3">C.3</a> Since draft-ietf-httpbis-p7-auth-01896 <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a> Since draft-ietf-httpbis-p7-auth-01 904 897 </h2> 905 <p id="rfc.section. C.3.p.1">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):898 <p id="rfc.section.B.3.p.1">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 906 899 </p> 907 900 <ul> … … 909 902 <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> 910 903 </ul> 911 <h2 id="rfc.section. C.4"><a href="#rfc.section.C.4">C.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2>912 <p id="rfc.section. C.4.p.1">Ongoing work on IANA Message Header Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>):904 <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2> 905 <p id="rfc.section.B.4.p.1">Ongoing work on IANA Message Header Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): 913 906 </p> 914 907 <ul> 915 908 <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li> 916 909 </ul> 917 <h2 id="rfc.section. C.5"><a href="#rfc.section.C.5">C.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2>918 <h2 id="rfc.section. C.6"><a href="#rfc.section.C.6">C.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2>919 <p id="rfc.section. C.6.p.1">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):910 <h2 id="rfc.section.B.5"><a href="#rfc.section.B.5">B.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2> 911 <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2> 912 <p id="rfc.section.B.6.p.1">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 920 913 </p> 921 914 <ul> … … 924 917 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 925 918 </ul> 926 <h2 id="rfc.section. C.7"><a href="#rfc.section.C.7">C.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></h2>927 <p id="rfc.section. C.7.p.1">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>):919 <h2 id="rfc.section.B.7"><a href="#rfc.section.B.7">B.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></h2> 920 <p id="rfc.section.B.7.p.1">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): 928 921 </p> 929 922 <ul> 930 923 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 931 924 </ul> 932 <h2 id="rfc.section. C.8"><a href="#rfc.section.C.8">C.8</a> <a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></h2>933 <p id="rfc.section. C.8.p.1">None.</p>934 <h2 id="rfc.section. C.9"><a href="#rfc.section.C.9">C.9</a> <a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></h2>935 <p id="rfc.section. C.9.p.1">Closed issues: </p>925 <h2 id="rfc.section.B.8"><a href="#rfc.section.B.8">B.8</a> <a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></h2> 926 <p id="rfc.section.B.8.p.1">None.</p> 927 <h2 id="rfc.section.B.9"><a href="#rfc.section.B.9">B.9</a> <a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></h2> 928 <p id="rfc.section.B.9.p.1">Closed issues: </p> 936 929 <ul> 937 930 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>>: "move IANA registrations for optional status codes" 938 931 </li> 939 932 </ul> 940 <h2 id="rfc.section. C.10"><a href="#rfc.section.C.10">C.10</a> <a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></h2>941 <p id="rfc.section. C.10.p.1">No significant changes.</p>942 <h2 id="rfc.section. C.11"><a href="#rfc.section.C.11">C.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></h2>943 <p id="rfc.section. C.11.p.1">Partly resolved issues: </p>933 <h2 id="rfc.section.B.10"><a href="#rfc.section.B.10">B.10</a> <a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></h2> 934 <p id="rfc.section.B.10.p.1">No significant changes.</p> 935 <h2 id="rfc.section.B.11"><a href="#rfc.section.B.11">B.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></h2> 936 <p id="rfc.section.B.11.p.1">Partly resolved issues: </p> 944 937 <ul> 945 938 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>>: "Term for the requested resource's URI" 946 939 </li> 947 940 </ul> 948 <h2 id="rfc.section. C.12"><a href="#rfc.section.C.12">C.12</a> <a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></h2>949 <p id="rfc.section. C.12.p.1">None yet.</p>941 <h2 id="rfc.section.B.12"><a href="#rfc.section.B.12">B.12</a> <a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></h2> 942 <p id="rfc.section.B.12.p.1">None yet.</p> 950 943 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 951 944 <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a> … … 1007 1000 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 1008 1001 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>7.1</b></a></li> 1009 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2"> C.1</a></li>1002 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>7.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li> 1010 1003 <li class="indline1"><em>RFC2617</em> <a class="iref" href="#rfc.xref.RFC2617.1">1</a>, <a class="iref" href="#rfc.xref.RFC2617.2">1</a>, <a class="iref" href="#rfc.xref.RFC2617.3">1.2.2</a>, <a class="iref" href="#rfc.xref.RFC2617.4">1.2.2</a>, <a class="iref" href="#rfc.xref.RFC2617.5">2.1</a>, <a class="iref" href="#rfc.xref.RFC2617.6">2.2</a>, <a class="iref" href="#rfc.xref.RFC2617.7">3.1</a>, <a class="iref" href="#rfc.xref.RFC2617.8">3.2</a>, <a class="iref" href="#rfc.xref.RFC2617.9">3.3</a>, <a class="iref" href="#rfc.xref.RFC2617.10">3.4</a>, <a class="iref" href="#RFC2617"><b>7.1</b></a><ul class="ind"> 1011 1004 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.RFC2617.3">1.2.2</a>, <a class="iref" href="#rfc.xref.RFC2617.4">1.2.2</a></li>
Note: See TracChangeset
for help on using the changeset viewer.