Changeset 1646 for draft-ietf-httpbis/latest
- Timestamp:
- 30/03/12 15:52:18 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1645 r1646 732 732 <li>8.2 <a href="#status.code.registration">Status Code Registry</a></li> 733 733 <li>8.3 <a href="#header.field.registration">Header Field Registration</a></li> 734 <li>8.4 <a href="#content.coding.registration">Content Coding Registry</a></li> 734 735 </ul> 735 736 </li> … … 739 740 <li>9.3 <a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li> 740 741 <li>9.4 <a href="#rfc.section.9.4">Security Considerations for CONNECT</a></li> 742 <li>9.5 <a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li> 741 743 </ul> 742 744 </li> … … 790 792 </ul> 791 793 </li> 792 <li>D.4 <a href="#IANA.considerations3">IANA Considerations</a><ul> 793 <li>D.4.1 <a href="#content.coding.registration">Content Coding Registry</a></li> 794 <li>D.4 <a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul> 795 <li>D.4.1 <a href="#mime-version">MIME-Version</a></li> 796 <li>D.4.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 797 <li>D.4.3 <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 798 <li>D.4.4 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 799 <li>D.4.5 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 800 <li>D.4.6 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 801 <li>D.4.7 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 794 802 </ul> 795 803 </li> 796 <li>D.5 <a href="#security.considerations3">Security Considerations</a><ul> 797 <li>D.5.1 <a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li> 798 </ul> 799 </li> 800 <li>D.6 <a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul> 801 <li>D.6.1 <a href="#mime-version">MIME-Version</a></li> 802 <li>D.6.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 803 <li>D.6.3 <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 804 <li>D.6.4 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 805 <li>D.6.5 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 806 <li>D.6.6 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 807 <li>D.6.7 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 808 </ul> 809 </li> 810 <li>D.7 <a href="#additional.features">Additional Features</a></li> 811 <li>D.8 <a href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></li> 812 <li>D.9 <a href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a><ul> 813 <li>D.9.1 <a href="#rfc.section.D.9.1">Since RFC 2616</a></li> 814 <li>D.9.2 <a href="#rfc.section.D.9.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 815 <li>D.9.3 <a href="#rfc.section.D.9.3">Since draft-ietf-httpbis-p3-payload-01</a></li> 816 <li>D.9.4 <a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li> 817 <li>D.9.5 <a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li> 818 <li>D.9.6 <a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li> 819 <li>D.9.7 <a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li> 820 <li>D.9.8 <a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li> 821 <li>D.9.9 <a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li> 822 <li>D.9.10 <a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li> 823 <li>D.9.11 <a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li> 824 <li>D.9.12 <a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li> 825 <li>D.9.13 <a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li> 826 <li>D.9.14 <a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li> 827 <li>D.9.15 <a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li> 828 <li>D.9.16 <a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li> 829 <li>D.9.17 <a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li> 830 <li>D.9.18 <a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li> 831 <li>D.9.19 <a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li> 832 <li>D.9.20 <a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li> 833 <li>D.9.21 <a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li> 804 <li>D.5 <a href="#additional.features">Additional Features</a></li> 805 <li>D.6 <a href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></li> 806 <li>D.7 <a href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a><ul> 807 <li>D.7.1 <a href="#rfc.section.D.7.1">Since RFC 2616</a></li> 808 <li>D.7.2 <a href="#rfc.section.D.7.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 809 <li>D.7.3 <a href="#rfc.section.D.7.3">Since draft-ietf-httpbis-p3-payload-01</a></li> 810 <li>D.7.4 <a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li> 811 <li>D.7.5 <a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li> 812 <li>D.7.6 <a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li> 813 <li>D.7.7 <a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li> 814 <li>D.7.8 <a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li> 815 <li>D.7.9 <a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li> 816 <li>D.7.10 <a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li> 817 <li>D.7.11 <a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li> 818 <li>D.7.12 <a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li> 819 <li>D.7.13 <a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li> 820 <li>D.7.14 <a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li> 821 <li>D.7.15 <a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li> 822 <li>D.7.16 <a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li> 823 <li>D.7.17 <a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li> 824 <li>D.7.18 <a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li> 825 <li>D.7.19 <a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li> 826 <li>D.7.20 <a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li> 827 <li>D.7.21 <a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li> 834 828 </ul> 835 829 </li> … … 2566 2560 </div> 2567 2561 <p id="rfc.section.7.4.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic 2568 preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields"> Appendix D.5.1</a>.2562 preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section 9.5</a>. 2569 2563 </p> 2570 2564 <p id="rfc.section.7.4.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice … … 3310 3304 <td class="left">http</td> 3311 3305 <td class="left">standard</td> 3312 <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix D. 6.1</a>3306 <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix D.4.1</a> 3313 3307 </td> 3314 3308 </tr> … … 3352 3346 </div> 3353 3347 <p id="rfc.section.8.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 3348 <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a> <a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2> 3349 <p id="rfc.section.8.4.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section 6.4.1</a> of this document. 3350 </p> 3351 <p id="rfc.section.8.4.p.2">The HTTP Content Codings Registry located at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>> shall be updated with the registration below: 3352 </p> 3353 <div id="rfc.table.4"> 3354 <div id="iana.content.coding.registration.table"></div> 3355 <table class="tt full left" cellpadding="3" cellspacing="0"> 3356 <thead> 3357 <tr> 3358 <th>Name</th> 3359 <th>Description</th> 3360 <th>Reference</th> 3361 </tr> 3362 </thead> 3363 <tbody> 3364 <tr> 3365 <td class="left">compress</td> 3366 <td class="left">UNIX "compress" program method</td> 3367 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 3368 </td> 3369 </tr> 3370 <tr> 3371 <td class="left">deflate</td> 3372 <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 3373 </td> 3374 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.52"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 3375 </td> 3376 </tr> 3377 <tr> 3378 <td class="left">gzip</td> 3379 <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 3380 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 3381 </td> 3382 </tr> 3383 <tr> 3384 <td class="left">identity</td> 3385 <td class="left">reserved (synonym for "no encoding" in Accept-Encoding header field)</td> 3386 <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section 7.3</a> 3387 </td> 3388 </tr> 3389 </tbody> 3390 </table> 3391 </div> 3354 3392 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 3355 3393 <p id="rfc.section.9.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 … … 3415 3453 A HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports. 3416 3454 </p> 3455 <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a> <a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2> 3456 <p id="rfc.section.9.5.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The Accept-Language header field 3457 in particular can reveal information the user would consider to be of a private nature, because the understanding of particular 3458 languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option 3459 to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged to let the 3460 configuration process include a message which makes the user aware of the loss of privacy involved. 3461 </p> 3462 <p id="rfc.section.9.5.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields 3463 by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by 3464 looking for any Vary header fields generated by the server, that such sending could improve the quality of service. 3465 </p> 3466 <p id="rfc.section.9.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be 3467 used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers 3468 to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions 3469 of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will 3470 also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to 3471 be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could 3472 filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved. 3473 </p> 3417 3474 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 3418 <p id="rfc.section.10.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.5 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.3475 <p id="rfc.section.10.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.54"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 3419 3476 </p> 3420 3477 <h1 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References … … 3660 3717 </p> 3661 3718 <p id="rfc.section.A.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 3662 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.5 2"><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 7.17</a>)3719 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.55"><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 7.17</a>) 3663 3720 </p> 3664 3721 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 4182 4239 <tr> 4183 4240 <td class="left">Content-Length</td> 4184 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.5 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>4241 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.56"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td> 4185 4242 </tr> 4186 4243 <tr> … … 4192 4249 </div> 4193 4250 <h3 id="rfc.section.D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a> <a id="payload.body" href="#payload.body">Payload Body</a></h3> 4194 <p id="rfc.section.D.1.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.5 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure4251 <p id="rfc.section.D.1.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure 4195 4252 safe and proper transfer of the message. 4196 4253 </p> … … 4348 4405 that doesn't conform to them is better than sending a 406 (Not Acceptable) response. 4349 4406 </p> 4350 <p id="rfc.section.D.3.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.5 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.4407 <p id="rfc.section.D.3.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information. 4351 4408 </p> 4352 4409 <p id="rfc.section.D.3.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities 4353 and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section 7.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 7.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding. 4" title="Accept-Encoding">Section 7.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section 7.4</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section 7.18</a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including aspects of the connection (e.g., IP address) or information4410 and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.4" title="Accept">Section 7.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 7.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section 7.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section 7.4</a>), and User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section 7.18</a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including aspects of the connection (e.g., IP address) or information 4354 4411 within extension header fields not defined by this specification. 4355 4412 </p> … … 4379 4436 when the server is unwilling or unable to provide a varying response using server-driven negotiation. 4380 4437 </p> 4381 <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="IANA.considerations3" href="#IANA.considerations3">IANA Considerations</a></h2> 4382 <h3 id="rfc.section.D.4.1"><a href="#rfc.section.D.4.1">D.4.1</a> <a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h3> 4383 <p id="rfc.section.D.4.1.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section 6.4.1</a> of this document. 4384 </p> 4385 <p id="rfc.section.D.4.1.p.2">The HTTP Content Codings Registry located at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>> shall be updated with the registration below: 4386 </p> 4387 <div id="rfc.table.4"> 4388 <div id="iana.content.coding.registration.table"></div> 4389 <table class="tt full left" cellpadding="3" cellspacing="0"> 4390 <thead> 4391 <tr> 4392 <th>Name</th> 4393 <th>Description</th> 4394 <th>Reference</th> 4395 </tr> 4396 </thead> 4397 <tbody> 4398 <tr> 4399 <td class="left">compress</td> 4400 <td class="left">UNIX "compress" program method</td> 4401 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.56"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 4402 </td> 4403 </tr> 4404 <tr> 4405 <td class="left">deflate</td> 4406 <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 4407 </td> 4408 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 4409 </td> 4410 </tr> 4411 <tr> 4412 <td class="left">gzip</td> 4413 <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 4414 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 4415 </td> 4416 </tr> 4417 <tr> 4418 <td class="left">identity</td> 4419 <td class="left">reserved (synonym for "no encoding" in Accept-Encoding header field)</td> 4420 <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.5" title="Accept-Encoding">Section 7.3</a> 4421 </td> 4422 </tr> 4423 </tbody> 4424 </table> 4425 </div> 4426 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="security.considerations3" href="#security.considerations3">Security Considerations</a></h2> 4427 <p id="rfc.section.D.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 4428 as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does 4429 make some suggestions for reducing security risks. 4430 </p> 4431 <h3 id="rfc.section.D.5.1"><a href="#rfc.section.D.5.1">D.5.1</a> <a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h3> 4432 <p id="rfc.section.D.5.1.p.1">Accept header fields can reveal information about the user to all servers which are accessed. The Accept-Language header field 4433 in particular can reveal information the user would consider to be of a private nature, because the understanding of particular 4434 languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option 4435 to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged to let the 4436 configuration process include a message which makes the user aware of the loss of privacy involved. 4437 </p> 4438 <p id="rfc.section.D.5.1.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields 4439 by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by 4440 looking for any Vary header fields generated by the server, that such sending could improve the quality of service. 4441 </p> 4442 <p id="rfc.section.D.5.1.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be 4443 used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers 4444 to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions 4445 of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will 4446 also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to 4447 be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could 4448 filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved. 4449 </p> 4450 <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h2> 4451 <p id="rfc.section.D.6.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However, 4438 <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h2> 4439 <p id="rfc.section.D.4.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However, 4452 4440 RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were 4453 4441 carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, 4454 4442 to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients. 4455 4443 </p> 4456 <p id="rfc.section.D. 6.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments4444 <p id="rfc.section.D.4.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments 4457 4445 to HTTP also need to be aware of the differences because some conversions might be required. 4458 4446 </p> 4459 4447 <div id="rfc.iref.m.10"></div> 4460 4448 <div id="rfc.iref.h.20"></div> 4461 <h3 id="rfc.section.D. 6.1"><a href="#rfc.section.D.6.1">D.6.1</a> <a id="mime-version" href="#mime-version">MIME-Version</a></h3>4462 <p id="rfc.section.D. 6.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message.4449 <h3 id="rfc.section.D.4.1"><a href="#rfc.section.D.4.1">D.4.1</a> <a id="mime-version" href="#mime-version">MIME-Version</a></h3> 4450 <p id="rfc.section.D.4.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message. 4463 4451 Use of the MIME-Version header field indicates that the message is in full conformance with the MIME protocol (as defined 4464 4452 in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full conformance (where possible) when exporting HTTP messages to strict … … 4466 4454 </p> 4467 4455 <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.59"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 4468 </pre><p id="rfc.section.D. 6.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this4456 </pre><p id="rfc.section.D.4.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this 4469 4457 document and not the MIME specification. 4470 4458 </p> 4471 <h3 id="rfc.section.D. 6.2"><a href="#rfc.section.D.6.2">D.6.2</a> <a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h3>4472 <p id="rfc.section.D. 6.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line4459 <h3 id="rfc.section.D.4.2"><a href="#rfc.section.D.4.2">D.4.2</a> <a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h3> 4460 <p id="rfc.section.D.4.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line 4473 4461 break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted 4474 4462 over HTTP. 4475 4463 </p> 4476 <p id="rfc.section.D. 6.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of4464 <p id="rfc.section.D.4.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of 4477 4465 a Content-Encoding and by the fact that HTTP allows the use of some character encodings which do not use octets 13 and 10 4478 4466 to represent CR and LF, respectively, as is the case for some multi-byte character encodings. 4479 4467 </p> 4480 <p id="rfc.section.D. 6.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in4468 <p id="rfc.section.D.4.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in 4481 4469 canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP. 4482 4470 </p> 4483 <h3 id="rfc.section.D. 6.3"><a href="#rfc.section.D.6.3">D.6.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h3>4484 <p id="rfc.section.D. 6.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section 6.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.4485 </p> 4486 <h3 id="rfc.section.D. 6.4"><a href="#rfc.section.D.6.4">D.6.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h3>4487 <p id="rfc.section.D. 6.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on4471 <h3 id="rfc.section.D.4.3"><a href="#rfc.section.D.4.3">D.4.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h3> 4472 <p id="rfc.section.D.4.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section 6.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 4473 </p> 4474 <h3 id="rfc.section.D.4.4"><a href="#rfc.section.D.4.4">D.4.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h3> 4475 <p id="rfc.section.D.4.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on 4488 4476 the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some 4489 4477 experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" … … 4492 4480 <div id="rfc.iref.c.11"></div> 4493 4481 <div id="rfc.iref.h.21"></div> 4494 <h3 id="rfc.section.D. 6.5"><a href="#rfc.section.D.6.5">D.6.5</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h3>4495 <p id="rfc.section.D. 6.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.4496 </p> 4497 <p id="rfc.section.D. 6.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct4482 <h3 id="rfc.section.D.4.5"><a href="#rfc.section.D.4.5">D.4.5</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h3> 4483 <p id="rfc.section.D.4.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client. 4484 </p> 4485 <p id="rfc.section.D.4.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct 4498 4486 format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol 4499 4487 being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over 4500 4488 the destination protocol. 4501 4489 </p> 4502 <h3 id="rfc.section.D. 6.6"><a href="#rfc.section.D.6.6">D.6.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3>4503 <p id="rfc.section.D. 6.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.59"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.4504 </p> 4505 <h3 id="rfc.section.D. 6.7"><a href="#rfc.section.D.6.7">D.6.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h3>4506 <p id="rfc.section.D. 6.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not4490 <h3 id="rfc.section.D.4.6"><a href="#rfc.section.D.4.6">D.4.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3> 4491 <p id="rfc.section.D.4.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.59"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 4492 </p> 4493 <h3 id="rfc.section.D.4.7"><a href="#rfc.section.D.4.7">D.4.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h3> 4494 <p id="rfc.section.D.4.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not 4507 4495 fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations 4508 4496 and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 6.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. 4509 4497 </p> 4510 <h2 id="rfc.section.D. 7"><a href="#rfc.section.D.7">D.7</a> <a id="additional.features" href="#additional.features">Additional Features</a></h2>4511 <p id="rfc.section.D. 7.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.14498 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="additional.features" href="#additional.features">Additional Features</a></h2> 4499 <p id="rfc.section.D.5.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1 4512 4500 applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 4513 4501 with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that 4514 4502 experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification. 4515 4503 </p> 4516 <p id="rfc.section.D. 7.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).4517 </p> 4518 <h2 id="rfc.section.D. 8"><a href="#rfc.section.D.8">D.8</a> <a id="changes.from.rfc.2616-3" href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></h2>4519 <p id="rfc.section.D. 8.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 6.3</a>)4520 </p> 4521 <p id="rfc.section.D. 8.p.2">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 6.4.1</a>)4522 </p> 4523 <p id="rfc.section.D. 8.p.3">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a>)4524 </p> 4525 <p id="rfc.section.D. 8.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>)4526 </p> 4527 <p id="rfc.section.D. 8.p.5">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses,4504 <p id="rfc.section.D.5.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>). 4505 </p> 4506 <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="changes.from.rfc.2616-3" href="#changes.from.rfc.2616-3">Changes from RFC 2616</a></h2> 4507 <p id="rfc.section.D.6.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 6.3</a>) 4508 </p> 4509 <p id="rfc.section.D.6.p.2">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 6.4.1</a>) 4510 </p> 4511 <p id="rfc.section.D.6.p.3">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 6.5.1</a>) 4512 </p> 4513 <p id="rfc.section.D.6.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 4514 </p> 4515 <p id="rfc.section.D.6.p.5">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses, 4528 4516 and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 4529 4517 </p> 4530 <p id="rfc.section.D. 8.p.6">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section 7.2</a>)4531 </p> 4532 <p id="rfc.section.D. 8.p.7">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken4518 <p id="rfc.section.D.6.p.6">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section 7.2</a>) 4519 </p> 4520 <p id="rfc.section.D.6.p.7">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken 4533 4521 servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking 4534 4522 relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section 7.8</a>) 4535 4523 </p> 4536 <p id="rfc.section.D. 8.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix D.6.5</a>)4537 </p> 4538 <p id="rfc.section.D. 8.p.9">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix D.7</a>)4539 </p> 4540 <h2 id="rfc.section.D. 9"><a href="#rfc.section.D.9">D.9</a> <a id="change.log3" href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a></h2>4541 <h3 id="rfc.section.D. 9.1"><a href="#rfc.section.D.9.1">D.9.1</a> Since RFC 26164524 <p id="rfc.section.D.6.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix D.4.5</a>) 4525 </p> 4526 <p id="rfc.section.D.6.p.9">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix D.5</a>) 4527 </p> 4528 <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="change.log3" href="#change.log3">Change Log (to be removed by RFC Editor before publication)</a></h2> 4529 <h3 id="rfc.section.D.7.1"><a href="#rfc.section.D.7.1">D.7.1</a> Since RFC 2616 4542 4530 </h3> 4543 <p id="rfc.section.D. 9.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.4544 </p> 4545 <h3 id="rfc.section.D. 9.2"><a href="#rfc.section.D.9.2">D.9.2</a> Since draft-ietf-httpbis-p3-payload-004531 <p id="rfc.section.D.7.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 4532 </p> 4533 <h3 id="rfc.section.D.7.2"><a href="#rfc.section.D.7.2">D.7.2</a> Since draft-ietf-httpbis-p3-payload-00 4546 4534 </h3> 4547 <p id="rfc.section.D. 9.2.p.1">Closed issues: </p>4535 <p id="rfc.section.D.7.2.p.1">Closed issues: </p> 4548 4536 <ul> 4549 4537 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>>: "Media Type Registrations" (<<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>>) … … 4570 4558 </li> 4571 4559 </ul> 4572 <h3 id="rfc.section.D. 9.3"><a href="#rfc.section.D.9.3">D.9.3</a> Since draft-ietf-httpbis-p3-payload-014560 <h3 id="rfc.section.D.7.3"><a href="#rfc.section.D.7.3">D.7.3</a> Since draft-ietf-httpbis-p3-payload-01 4573 4561 </h3> 4574 <p id="rfc.section.D. 9.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>>):4562 <p id="rfc.section.D.7.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>>): 4575 4563 </p> 4576 4564 <ul> 4577 4565 <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> 4578 4566 </ul> 4579 <h3 id="rfc.section.D. 9.4"><a href="#rfc.section.D.9.4">D.9.4</a> <a id="changes.3.since.02" href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h3>4580 <p id="rfc.section.D. 9.4.p.1">Closed issues: </p>4567 <h3 id="rfc.section.D.7.4"><a href="#rfc.section.D.7.4">D.7.4</a> <a id="changes.3.since.02" href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h3> 4568 <p id="rfc.section.D.7.4.p.1">Closed issues: </p> 4581 4569 <ul> 4582 4570 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>>: "Quoting Charsets" … … 4587 4575 </li> 4588 4576 </ul> 4589 <p id="rfc.section.D. 9.4.p.2">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>):4577 <p id="rfc.section.D.7.4.p.2">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): 4590 4578 </p> 4591 4579 <ul> 4592 4580 <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li> 4593 4581 </ul> 4594 <h3 id="rfc.section.D. 9.5"><a href="#rfc.section.D.9.5">D.9.5</a> <a id="changes.3.since.03" href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h3>4595 <p id="rfc.section.D. 9.5.p.1">Closed issues: </p>4582 <h3 id="rfc.section.D.7.5"><a href="#rfc.section.D.7.5">D.7.5</a> <a id="changes.3.since.03" href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h3> 4583 <p id="rfc.section.D.7.5.p.1">Closed issues: </p> 4596 4584 <ul> 4597 4585 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>>: "Quoting Charsets" … … 4602 4590 </li> 4603 4591 </ul> 4604 <p id="rfc.section.D. 9.5.p.2">Other changes: </p>4592 <p id="rfc.section.D.7.5.p.2">Other changes: </p> 4605 4593 <ul> 4606 4594 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>>: "Encoding References Normative" — rephrase the annotation and reference BCP97. 4607 4595 </li> 4608 4596 </ul> 4609 <h3 id="rfc.section.D. 9.6"><a href="#rfc.section.D.9.6">D.9.6</a> <a id="changes.3.since.04" href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h3>4610 <p id="rfc.section.D. 9.6.p.1">Closed issues: </p>4597 <h3 id="rfc.section.D.7.6"><a href="#rfc.section.D.7.6">D.7.6</a> <a id="changes.3.since.04" href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h3> 4598 <p id="rfc.section.D.7.6.p.1">Closed issues: </p> 4611 4599 <ul> 4612 4600 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>>: "RFC 2822 is updated by RFC 5322" 4613 4601 </li> 4614 4602 </ul> 4615 <p id="rfc.section.D. 9.6.p.2">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>>):4603 <p id="rfc.section.D.7.6.p.2">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>>): 4616 4604 </p> 4617 4605 <ul> … … 4620 4608 <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li> 4621 4609 </ul> 4622 <h3 id="rfc.section.D. 9.7"><a href="#rfc.section.D.9.7">D.9.7</a> <a id="changes.3.since.05" href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h3>4623 <p id="rfc.section.D. 9.7.p.1">Closed issues: </p>4610 <h3 id="rfc.section.D.7.7"><a href="#rfc.section.D.7.7">D.7.7</a> <a id="changes.3.since.05" href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h3> 4611 <p id="rfc.section.D.7.7.p.1">Closed issues: </p> 4624 4612 <ul> 4625 4613 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>>: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?" 4626 4614 </li> 4627 4615 </ul> 4628 <p id="rfc.section.D. 9.7.p.2">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>>):4616 <p id="rfc.section.D.7.7.p.2">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>>): 4629 4617 </p> 4630 4618 <ul> 4631 4619 <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> 4632 4620 </ul> 4633 <p id="rfc.section.D. 9.7.p.3">Other changes: </p>4621 <p id="rfc.section.D.7.7.p.3">Other changes: </p> 4634 4622 <ul> 4635 4623 <li>Move definition of quality values into Part 1.</li> 4636 4624 </ul> 4637 <h3 id="rfc.section.D. 9.8"><a href="#rfc.section.D.9.8">D.9.8</a> <a id="changes.3.since.06" href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h3>4638 <p id="rfc.section.D. 9.8.p.1">Closed issues: </p>4625 <h3 id="rfc.section.D.7.8"><a href="#rfc.section.D.7.8">D.7.8</a> <a id="changes.3.since.06" href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h3> 4626 <p id="rfc.section.D.7.8.p.1">Closed issues: </p> 4639 4627 <ul> 4640 4628 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>>: "Content-Location isn't special" … … 4643 4631 </li> 4644 4632 </ul> 4645 <h3 id="rfc.section.D. 9.9"><a href="#rfc.section.D.9.9">D.9.9</a> <a id="changes.3.since.07" href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h3>4646 <p id="rfc.section.D. 9.9.p.1">Closed issues: </p>4633 <h3 id="rfc.section.D.7.9"><a href="#rfc.section.D.7.9">D.7.9</a> <a id="changes.3.since.07" href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h3> 4634 <p id="rfc.section.D.7.9.p.1">Closed issues: </p> 4647 4635 <ul> 4648 4636 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>>: "Updated reference for language tags" … … 4659 4647 </li> 4660 4648 </ul> 4661 <p id="rfc.section.D. 9.9.p.2">Partly resolved issues: </p>4649 <p id="rfc.section.D.7.9.p.2">Partly resolved issues: </p> 4662 4650 <ul> 4663 4651 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>>: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection) … … 4666 4654 </li> 4667 4655 </ul> 4668 <h3 id="rfc.section.D. 9.10"><a href="#rfc.section.D.9.10">D.9.10</a> <a id="changes.3.since.08" href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h3>4669 <p id="rfc.section.D. 9.10.p.1">Closed issues: </p>4656 <h3 id="rfc.section.D.7.10"><a href="#rfc.section.D.7.10">D.7.10</a> <a id="changes.3.since.08" href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h3> 4657 <p id="rfc.section.D.7.10.p.1">Closed issues: </p> 4670 4658 <ul> 4671 4659 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>>: "Content Negotiation for media types" … … 4674 4662 </li> 4675 4663 </ul> 4676 <h3 id="rfc.section.D. 9.11"><a href="#rfc.section.D.9.11">D.9.11</a> <a id="changes.3.since.09" href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h3>4677 <p id="rfc.section.D. 9.11.p.1">Closed issues: </p>4664 <h3 id="rfc.section.D.7.11"><a href="#rfc.section.D.7.11">D.7.11</a> <a id="changes.3.since.09" href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h3> 4665 <p id="rfc.section.D.7.11.p.1">Closed issues: </p> 4678 4666 <ul> 4679 4667 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>>: "MIME-Version not listed in P1, general header fields" … … 4686 4674 </li> 4687 4675 </ul> 4688 <p id="rfc.section.D. 9.11.p.2">Partly resolved issues: </p>4676 <p id="rfc.section.D.7.11.p.2">Partly resolved issues: </p> 4689 4677 <ul> 4690 4678 <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" 4691 4679 </li> 4692 4680 </ul> 4693 <h3 id="rfc.section.D. 9.12"><a href="#rfc.section.D.9.12">D.9.12</a> <a id="changes.3.since.10" href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h3>4694 <p id="rfc.section.D. 9.12.p.1">Closed issues: </p>4681 <h3 id="rfc.section.D.7.12"><a href="#rfc.section.D.7.12">D.7.12</a> <a id="changes.3.since.10" href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h3> 4682 <p id="rfc.section.D.7.12.p.1">Closed issues: </p> 4695 4683 <ul> 4696 4684 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>>: "Clarify 'Requested Variant'" … … 4711 4699 </li> 4712 4700 </ul> 4713 <p id="rfc.section.D. 9.12.p.2">Partly resolved issues: </p>4701 <p id="rfc.section.D.7.12.p.2">Partly resolved issues: </p> 4714 4702 <ul> 4715 4703 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>>: "Content-MD5 and partial responses" 4716 4704 </li> 4717 4705 </ul> 4718 <h3 id="rfc.section.D. 9.13"><a href="#rfc.section.D.9.13">D.9.13</a> <a id="changes.3.since.11" href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h3>4719 <p id="rfc.section.D. 9.13.p.1">Closed issues: </p>4706 <h3 id="rfc.section.D.7.13"><a href="#rfc.section.D.7.13">D.7.13</a> <a id="changes.3.since.11" href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h3> 4707 <p id="rfc.section.D.7.13.p.1">Closed issues: </p> 4720 4708 <ul> 4721 4709 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>>: "Factor out Content-Disposition" 4722 4710 </li> 4723 4711 </ul> 4724 <h3 id="rfc.section.D. 9.14"><a href="#rfc.section.D.9.14">D.9.14</a> <a id="changes.3.since.12" href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h3>4725 <p id="rfc.section.D. 9.14.p.1">Closed issues: </p>4712 <h3 id="rfc.section.D.7.14"><a href="#rfc.section.D.7.14">D.7.14</a> <a id="changes.3.since.12" href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h3> 4713 <p id="rfc.section.D.7.14.p.1">Closed issues: </p> 4726 4714 <ul> 4727 4715 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification" … … 4732 4720 </li> 4733 4721 </ul> 4734 <h3 id="rfc.section.D. 9.15"><a href="#rfc.section.D.9.15">D.9.15</a> <a id="changes.3.since.13" href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h3>4735 <p id="rfc.section.D. 9.15.p.1">Closed issues: </p>4722 <h3 id="rfc.section.D.7.15"><a href="#rfc.section.D.7.15">D.7.15</a> <a id="changes.3.since.13" href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h3> 4723 <p id="rfc.section.D.7.15.p.1">Closed issues: </p> 4736 4724 <ul> 4737 4725 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/20">http://tools.ietf.org/wg/httpbis/trac/ticket/20</a>>: "Default charsets for text media types" … … 4744 4732 </li> 4745 4733 </ul> 4746 <h3 id="rfc.section.D. 9.16"><a href="#rfc.section.D.9.16">D.9.16</a> <a id="changes.3.since.14" href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h3>4747 <p id="rfc.section.D. 9.16.p.1">None.</p>4748 <h3 id="rfc.section.D. 9.17"><a href="#rfc.section.D.9.17">D.9.17</a> <a id="changes.3.since.15" href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h3>4749 <p id="rfc.section.D. 9.17.p.1">Closed issues: </p>4734 <h3 id="rfc.section.D.7.16"><a href="#rfc.section.D.7.16">D.7.16</a> <a id="changes.3.since.14" href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h3> 4735 <p id="rfc.section.D.7.16.p.1">None.</p> 4736 <h3 id="rfc.section.D.7.17"><a href="#rfc.section.D.7.17">D.7.17</a> <a id="changes.3.since.15" href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h3> 4737 <p id="rfc.section.D.7.17.p.1">Closed issues: </p> 4750 4738 <ul> 4751 4739 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>>: "Strength of requirements on Accept re: 406" 4752 4740 </li> 4753 4741 </ul> 4754 <h3 id="rfc.section.D. 9.18"><a href="#rfc.section.D.9.18">D.9.18</a> <a id="changes.3.since.16" href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h3>4755 <p id="rfc.section.D. 9.18.p.1">Closed issues: </p>4742 <h3 id="rfc.section.D.7.18"><a href="#rfc.section.D.7.18">D.7.18</a> <a id="changes.3.since.16" href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h3> 4743 <p id="rfc.section.D.7.18.p.1">Closed issues: </p> 4756 4744 <ul> 4757 4745 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>>: "Document HTTP's error-handling philosophy" 4758 4746 </li> 4759 4747 </ul> 4760 <h3 id="rfc.section.D. 9.19"><a href="#rfc.section.D.9.19">D.9.19</a> <a id="changes.3.since.17" href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h3>4761 <p id="rfc.section.D. 9.19.p.1">Closed issues: </p>4748 <h3 id="rfc.section.D.7.19"><a href="#rfc.section.D.7.19">D.7.19</a> <a id="changes.3.since.17" href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h3> 4749 <p id="rfc.section.D.7.19.p.1">Closed issues: </p> 4762 4750 <ul> 4763 4751 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>>: "intended maturity level vs normative references" 4764 4752 </li> 4765 4753 </ul> 4766 <h3 id="rfc.section.D. 9.20"><a href="#rfc.section.D.9.20">D.9.20</a> <a id="changes.3.since.18" href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h3>4767 <p id="rfc.section.D. 9.20.p.1">Closed issues: </p>4754 <h3 id="rfc.section.D.7.20"><a href="#rfc.section.D.7.20">D.7.20</a> <a id="changes.3.since.18" href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h3> 4755 <p id="rfc.section.D.7.20.p.1">Closed issues: </p> 4768 4756 <ul> 4769 4757 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>>: "is ETag a representation header field?" … … 4774 4762 </li> 4775 4763 </ul> 4776 <h3 id="rfc.section.D. 9.21"><a href="#rfc.section.D.9.21">D.9.21</a> <a id="changes.3.since.19" href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></h3>4777 <p id="rfc.section.D. 9.21.p.1">None yet.</p>4764 <h3 id="rfc.section.D.7.21"><a href="#rfc.section.D.7.21">D.7.21</a> <a id="changes.3.since.19" href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></h3> 4765 <p id="rfc.section.D.7.21.p.1">None yet.</p> 4778 4766 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 4779 4767 <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</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.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</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.T">T</a> <a href="#rfc.index.U">U</a> … … 4835 4823 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 4836 4824 <li>Accept header field <a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.iref.a.1"><b>7.1</b></a>, <a href="#rfc.xref.header.accept.3">8.3</a>, <a href="#rfc.xref.header.accept.4">D.3.1</a></li> 4837 <li>Accept-Charset header field <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.a.2"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3">D.3.1</a>, <a href="#rfc.xref.header.accept-charset.4">D. 8</a></li>4838 <li>Accept-Encoding header field <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.a.3"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4"> D.3.1</a>, <a href="#rfc.xref.header.accept-encoding.5">D.4.1</a></li>4825 <li>Accept-Charset header field <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.a.2"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3">D.3.1</a>, <a href="#rfc.xref.header.accept-charset.4">D.6</a></li> 4826 <li>Accept-Encoding header field <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.a.3"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4">8.4</a>, <a href="#rfc.xref.header.accept-encoding.5">D.3.1</a></li> 4839 4827 <li>Accept-Language header field <a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.iref.a.4"><b>7.4</b></a>, <a href="#rfc.xref.header.accept-language.2">8.3</a>, <a href="#rfc.xref.header.accept-language.3">D.3.1</a></li> 4840 4828 <li>Allow header field <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.5"><b>7.5</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li> … … 4854 4842 <li>Content-Encoding header field <a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.iref.c.7"><b>7.6</b></a>, <a href="#rfc.xref.header.content-encoding.2">7.6</a>, <a href="#rfc.xref.header.content-encoding.3">8.3</a>, <a href="#rfc.xref.header.content-encoding.4">D.2.1</a></li> 4855 4843 <li>Content-Language header field <a href="#rfc.iref.c.8"><b>7.7</b></a>, <a href="#rfc.xref.header.content-language.1">8.3</a>, <a href="#rfc.xref.header.content-language.2">D.2.1</a></li> 4856 <li>Content-Location header field <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.c.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4">D.2.1</a>, <a href="#rfc.xref.header.content-location.5">D. 8</a></li>4857 <li>Content-Transfer-Encoding header field <a href="#rfc.iref.c.11">D. 6.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">D.8</a></li>4844 <li>Content-Location header field <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.c.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4">D.2.1</a>, <a href="#rfc.xref.header.content-location.5">D.6</a></li> 4845 <li>Content-Transfer-Encoding header field <a href="#rfc.iref.c.11">D.4.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">D.6</a></li> 4858 4846 <li>Content-Type header field <a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.iref.c.10"><b>7.9</b></a>, <a href="#rfc.xref.header.content-type.4">8.3</a>, <a href="#rfc.xref.header.content-type.5">D.2.1</a></li> 4859 4847 </ul> … … 4921 4909 <li><tt>media-type</tt> <a href="#rfc.iref.g.24"><b>6.5</b></a></li> 4922 4910 <li><tt>method</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> 4923 <li><tt>MIME-Version</tt> <a href="#rfc.iref.g.59"><b>D. 6.1</b></a></li>4911 <li><tt>MIME-Version</tt> <a href="#rfc.iref.g.59"><b>D.4.1</b></a></li> 4924 4912 <li><tt>minute</tt> <a href="#rfc.iref.g.8"><b>6.1</b></a></li> 4925 4913 <li><tt>month</tt> <a href="#rfc.iref.g.13"><b>6.1</b></a></li> … … 4950 4938 <ul> 4951 4939 <li>Accept <a href="#rfc.xref.header.accept.1">3.2</a>, <a href="#rfc.xref.header.accept.2">6.5</a>, <a href="#rfc.iref.h.2"><b>7.1</b></a>, <a href="#rfc.xref.header.accept.3">8.3</a>, <a href="#rfc.xref.header.accept.4">D.3.1</a></li> 4952 <li>Accept-Charset <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3">D.3.1</a>, <a href="#rfc.xref.header.accept-charset.4">D. 8</a></li>4953 <li>Accept-Encoding <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4"> D.3.1</a>, <a href="#rfc.xref.header.accept-encoding.5">D.4.1</a></li>4940 <li>Accept-Charset <a href="#rfc.xref.header.accept-charset.1">3.2</a>, <a href="#rfc.iref.h.3"><b>7.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">8.3</a>, <a href="#rfc.xref.header.accept-charset.3">D.3.1</a>, <a href="#rfc.xref.header.accept-charset.4">D.6</a></li> 4941 <li>Accept-Encoding <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">6.4</a>, <a href="#rfc.iref.h.4"><b>7.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">8.3</a>, <a href="#rfc.xref.header.accept-encoding.4">8.4</a>, <a href="#rfc.xref.header.accept-encoding.5">D.3.1</a></li> 4954 4942 <li>Accept-Language <a href="#rfc.xref.header.accept-language.1">3.2</a>, <a href="#rfc.iref.h.5"><b>7.4</b></a>, <a href="#rfc.xref.header.accept-language.2">8.3</a>, <a href="#rfc.xref.header.accept-language.3">D.3.1</a></li> 4955 4943 <li>Allow <a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.6"><b>7.5</b></a>, <a href="#rfc.xref.header.allow.3">8.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li> 4956 4944 <li>Content-Encoding <a href="#rfc.xref.header.content-encoding.1">6.4</a>, <a href="#rfc.iref.h.7"><b>7.6</b></a>, <a href="#rfc.xref.header.content-encoding.2">7.6</a>, <a href="#rfc.xref.header.content-encoding.3">8.3</a>, <a href="#rfc.xref.header.content-encoding.4">D.2.1</a></li> 4957 4945 <li>Content-Language <a href="#rfc.iref.h.8"><b>7.7</b></a>, <a href="#rfc.xref.header.content-language.1">8.3</a>, <a href="#rfc.xref.header.content-language.2">D.2.1</a></li> 4958 <li>Content-Location <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4">D.2.1</a>, <a href="#rfc.xref.header.content-location.5">D. 8</a></li>4959 <li>Content-Transfer-Encoding <a href="#rfc.iref.h.21">D. 6.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">D.8</a></li>4946 <li>Content-Location <a href="#rfc.xref.header.content-location.1">2.3.4</a>, <a href="#rfc.iref.h.9"><b>7.8</b></a>, <a href="#rfc.xref.header.content-location.2">7.13</a>, <a href="#rfc.xref.header.content-location.3">8.3</a>, <a href="#rfc.xref.header.content-location.4">D.2.1</a>, <a href="#rfc.xref.header.content-location.5">D.6</a></li> 4947 <li>Content-Transfer-Encoding <a href="#rfc.iref.h.21">D.4.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">D.6</a></li> 4960 4948 <li>Content-Type <a href="#rfc.xref.header.content-type.1">3.1</a>, <a href="#rfc.xref.header.content-type.2">4</a>, <a href="#rfc.xref.header.content-type.3">6.5</a>, <a href="#rfc.iref.h.10"><b>7.9</b></a>, <a href="#rfc.xref.header.content-type.4">8.3</a>, <a href="#rfc.xref.header.content-type.5">D.2.1</a></li> 4961 4949 <li>Date <a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.11"><b>7.10</b></a>, <a href="#rfc.xref.header.date.2">8.3</a></li> … … 4964 4952 <li>Location <a href="#rfc.xref.header.location.1">2.3.4</a>, <a href="#rfc.xref.header.location.2">3.3</a>, <a href="#rfc.xref.header.location.3">4.5</a>, <a href="#rfc.iref.h.14"><b>7.13</b></a>, <a href="#rfc.xref.header.location.4">8.3</a>, <a href="#rfc.xref.header.location.5">A</a></li> 4965 4953 <li>Max-Forwards <a href="#rfc.xref.header.max-forwards.1">2.3.1</a>, <a href="#rfc.xref.header.max-forwards.2">2.3.7</a>, <a href="#rfc.xref.header.max-forwards.3">3.2</a>, <a href="#rfc.iref.h.15"><b>7.14</b></a>, <a href="#rfc.xref.header.max-forwards.4">8.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li> 4966 <li>MIME-Version <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.h.20"><b>D. 6.1</b></a></li>4954 <li>MIME-Version <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.h.20"><b>D.4.1</b></a></li> 4967 4955 <li>Referer <a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.16"><b>7.15</b></a>, <a href="#rfc.xref.header.referer.2">8.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li> 4968 4956 <li>Retry-After <a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">4.7.4</a>, <a href="#rfc.iref.h.17"><b>7.16</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3</a></li> … … 4995 4983 </ul> 4996 4984 </li> 4997 <li>MIME-Version header field <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.m.10"><b>D. 6.1</b></a></li>4985 <li>MIME-Version header field <a href="#rfc.xref.mime-version.1">8.3</a>, <a href="#rfc.iref.m.10"><b>D.4.1</b></a></li> 4998 4986 </ul> 4999 4987 </li> … … 5003 4991 </li> 5004 4992 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 5005 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.8</a>, <a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.33">4.4.4</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.35">4.6.15</a>, <a href="#rfc.xref.Part1.36">4.7.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.38">5.1</a>, <a href="#rfc.xref.Part1.39">6.4</a>, <a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.42">6.4.1</a>, <a href="#rfc.xref.Part1.43">6.4.1</a>, <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.46">7.8</a>, <a href="#rfc.xref.Part1.47">7.11</a>, <a href="#rfc.xref.Part1.48">7.17</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.50">7.18</a>, <a href="#rfc.xref.Part1.51"> 10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.52">A</a>, <a href="#rfc.xref.Part1.53">D.1.1</a>, <a href="#rfc.xref.Part1.54">D.1.2</a>, <a href="#rfc.xref.Part1.55">D.3.1</a>, <a href="#rfc.xref.Part1.56">D.4.1</a>, <a href="#rfc.xref.Part1.57">D.4.1</a>, <a href="#rfc.xref.Part1.58">D.4.1</a>, <a href="#rfc.xref.Part1.59">D.6.6</a><ul>4993 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.8</a>, <a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.33">4.4.4</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.35">4.6.15</a>, <a href="#rfc.xref.Part1.36">4.7.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.38">5.1</a>, <a href="#rfc.xref.Part1.39">6.4</a>, <a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.42">6.4.1</a>, <a href="#rfc.xref.Part1.43">6.4.1</a>, <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.46">7.8</a>, <a href="#rfc.xref.Part1.47">7.11</a>, <a href="#rfc.xref.Part1.48">7.17</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.50">7.18</a>, <a href="#rfc.xref.Part1.51">8.4</a>, <a href="#rfc.xref.Part1.52">8.4</a>, <a href="#rfc.xref.Part1.53">8.4</a>, <a href="#rfc.xref.Part1.54">10</a>, <a href="#Part1"><b>11.1</b></a>, <a href="#rfc.xref.Part1.55">A</a>, <a href="#rfc.xref.Part1.56">D.1.1</a>, <a href="#rfc.xref.Part1.57">D.1.2</a>, <a href="#rfc.xref.Part1.58">D.3.1</a>, <a href="#rfc.xref.Part1.59">D.4.6</a><ul> 5006 4994 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.3</a></li> 5007 4995 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> … … 5013 5001 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.24">3.1</a></li> 5014 5002 <li><em>Section 3.2.5</em> <a href="#rfc.xref.Part1.23">3.1</a></li> 5015 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.5 4">D.1.2</a></li>5016 <li><em>Section 3.3.1</em> <a href="#rfc.xref.Part1.59">D. 6.6</a></li>5017 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.5 3">D.1.1</a></li>5003 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.37">5</a>, <a href="#rfc.xref.Part1.57">D.1.2</a></li> 5004 <li><em>Section 3.3.1</em> <a href="#rfc.xref.Part1.59">D.4.6</a></li> 5005 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.56">D.1.1</a></li> 5018 5006 <li><em>Section 4</em> <a href="#rfc.xref.Part1.42">6.4.1</a></li> 5019 5007 <li><em>Section 4.1</em> <a href="#rfc.xref.Part1.27">3.1</a></li> 5020 <li><em>Section 4.2.1</em> <a href="#rfc.xref.Part1.39">6.4</a>, <a href="#rfc.xref.Part1.5 6">D.4.1</a></li>5008 <li><em>Section 4.2.1</em> <a href="#rfc.xref.Part1.39">6.4</a>, <a href="#rfc.xref.Part1.51">8.4</a></li> 5021 5009 <li><em>Section 4.2</em> <a href="#rfc.xref.Part1.43">6.4.1</a></li> 5022 <li><em>Section 4.2.2</em> <a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.5 7">D.4.1</a></li>5023 <li><em>Section 4.2.3</em> <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.5 8">D.4.1</a></li>5010 <li><em>Section 4.2.2</em> <a href="#rfc.xref.Part1.40">6.4</a>, <a href="#rfc.xref.Part1.52">8.4</a></li> 5011 <li><em>Section 4.2.3</em> <a href="#rfc.xref.Part1.41">6.4</a>, <a href="#rfc.xref.Part1.53">8.4</a></li> 5024 5012 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.29">3.2</a></li> 5025 <li><em>Section 4.3.1</em> <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.5 5">D.3.1</a></li>5013 <li><em>Section 4.3.1</em> <a href="#rfc.xref.Part1.44">7.1</a>, <a href="#rfc.xref.Part1.45">7.3</a>, <a href="#rfc.xref.Part1.58">D.3.1</a></li> 5026 5014 <li><em>Section 5.3</em> <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.21">2.3.8</a></li> 5027 5015 <li><em>Section 5.4</em> <a href="#rfc.xref.Part1.28">3.2</a></li> 5028 5016 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.38">5.1</a>, <a href="#rfc.xref.Part1.46">7.8</a></li> 5029 5017 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.26">3.1</a></li> 5030 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.5 2">A</a></li>5018 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.49">7.17</a>, <a href="#rfc.xref.Part1.55">A</a></li> 5031 5019 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.47">7.11</a></li> 5032 5020 <li><em>Section 6.5</em> <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.35">4.6.15</a></li> 5033 5021 <li><em>Section 7.3.1</em> <a href="#rfc.xref.Part1.20">2.3.7</a></li> 5034 <li><em>Section 9</em> <a href="#rfc.xref.Part1.5 1">10</a></li>5022 <li><em>Section 9</em> <a href="#rfc.xref.Part1.54">10</a></li> 5035 5023 </ul> 5036 5024 </li> … … 5092 5080 </ul> 5093 5081 </li> 5094 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.2">D. 7</a><ul>5082 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">4.5</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.2">D.5</a><ul> 5095 5083 <li><em>Section 9.3</em> <a href="#rfc.xref.RFC1945.1">4.5</a></li> 5096 5084 </ul> 5097 5085 </li> 5098 <li><em>RFC1950</em> <a href="# RFC1950"><b>11.1</b></a>, <a href="#rfc.xref.RFC1950.1">D.4.1</a></li>5099 <li><em>RFC1951</em> <a href="# RFC1951"><b>11.1</b></a>, <a href="#rfc.xref.RFC1951.1">D.4.1</a></li>5100 <li><em>RFC1952</em> <a href="# RFC1952"><b>11.1</b></a>, <a href="#rfc.xref.RFC1952.1">D.4.1</a></li>5101 <li><em>RFC2045</em> <a href="#RFC2045"><b>11.1</b></a>, <a href="#rfc.xref.RFC2045.1">D. 6</a>, <a href="#rfc.xref.RFC2045.2">D.6.1</a></li>5102 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">6.5</a>, <a href="#rfc.xref.RFC2046.2">6.5.2</a>, <a href="#RFC2046"><b>11.1</b></a>, <a href="#rfc.xref.RFC2046.3">D.2.2</a>, <a href="#rfc.xref.RFC2046.4">D. 6.2</a><ul>5086 <li><em>RFC1950</em> <a href="#rfc.xref.RFC1950.1">8.4</a>, <a href="#RFC1950"><b>11.1</b></a></li> 5087 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">8.4</a>, <a href="#RFC1951"><b>11.1</b></a></li> 5088 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">8.4</a>, <a href="#RFC1952"><b>11.1</b></a></li> 5089 <li><em>RFC2045</em> <a href="#RFC2045"><b>11.1</b></a>, <a href="#rfc.xref.RFC2045.1">D.4</a>, <a href="#rfc.xref.RFC2045.2">D.4.1</a></li> 5090 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">6.5</a>, <a href="#rfc.xref.RFC2046.2">6.5.2</a>, <a href="#RFC2046"><b>11.1</b></a>, <a href="#rfc.xref.RFC2046.3">D.2.2</a>, <a href="#rfc.xref.RFC2046.4">D.4.2</a><ul> 5103 5091 <li><em>Section 4.5.1</em> <a href="#rfc.xref.RFC2046.3">D.2.2</a></li> 5104 5092 <li><em>Section 5.1.1</em> <a href="#rfc.xref.RFC2046.2">6.5.2</a></li> 5105 5093 </ul> 5106 5094 </li> 5107 <li><em>RFC2049</em> <a href="#RFC2049"><b>11.2</b></a>, <a href="#rfc.xref.RFC2049.1">D. 6.2</a><ul>5108 <li><em>Section 4</em> <a href="#rfc.xref.RFC2049.1">D. 6.2</a></li>5095 <li><em>RFC2049</em> <a href="#RFC2049"><b>11.2</b></a>, <a href="#rfc.xref.RFC2049.1">D.4.2</a><ul> 5096 <li><em>Section 4</em> <a href="#rfc.xref.RFC2049.1">D.4.2</a></li> 5109 5097 </ul> 5110 5098 </li> 5111 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4.5</a>, <a href="#rfc.xref.RFC2068.2">4.5</a>, <a href="#RFC2068"><b>11.2</b></a>, <a href="#rfc.xref.RFC2068.3">D. 7</a><ul>5099 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">4.5</a>, <a href="#rfc.xref.RFC2068.2">4.5</a>, <a href="#RFC2068"><b>11.2</b></a>, <a href="#rfc.xref.RFC2068.3">D.5</a><ul> 5112 5100 <li><em>Section 10.3</em> <a href="#rfc.xref.RFC2068.2">4.5</a></li> 5113 5101 <li><em>Section 10.3.4</em> <a href="#rfc.xref.RFC2068.1">4.5</a></li> 5114 5102 </ul> 5115 5103 </li> 5116 <li><em>RFC2076</em> <a href="#RFC2076"><b>11.2</b></a>, <a href="#rfc.xref.RFC2076.1">D. 7</a></li>5104 <li><em>RFC2076</em> <a href="#RFC2076"><b>11.2</b></a>, <a href="#rfc.xref.RFC2076.1">D.5</a></li> 5117 5105 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>11.1</b></a></li> 5118 5106 <li><em>RFC2277</em> <a href="#rfc.xref.RFC2277.1">6.3</a>, <a href="#RFC2277"><b>11.2</b></a></li> 5119 5107 <li><em>RFC2295</em> <a href="#RFC2295"><b>11.2</b></a>, <a href="#rfc.xref.RFC2295.1">D.3</a></li> 5120 5108 <li><em>RFC2388</em> <a href="#rfc.xref.RFC2388.1">6.5.2</a>, <a href="#RFC2388"><b>11.2</b></a></li> 5121 <li><em>RFC2557</em> <a href="#rfc.xref.RFC2557.1">7.8</a>, <a href="#RFC2557"><b>11.2</b></a>, <a href="#rfc.xref.RFC2557.2">D. 6.7</a><ul>5109 <li><em>RFC2557</em> <a href="#rfc.xref.RFC2557.1">7.8</a>, <a href="#RFC2557"><b>11.2</b></a>, <a href="#rfc.xref.RFC2557.2">D.4.7</a><ul> 5122 5110 <li><em>Section 4</em> <a href="#rfc.xref.RFC2557.1">7.8</a></li> 5123 5111 </ul> 5124 5112 </li> 5125 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#rfc.xref.RFC2616.3">7.4</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.4">C.1</a>, <a href="#rfc.xref.RFC2616.5">D. 9.1</a><ul>5113 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#rfc.xref.RFC2616.3">7.4</a>, <a href="#RFC2616"><b>11.2</b></a>, <a href="#rfc.xref.RFC2616.4">C.1</a>, <a href="#rfc.xref.RFC2616.5">D.7.1</a><ul> 5126 5114 <li><em>Section 10.3.8</em> <a href="#rfc.xref.RFC2616.2">4.5</a></li> 5127 5115 <li><em>Section 14.4</em> <a href="#rfc.xref.RFC2616.3">7.4</a></li> … … 5158 5146 </ul> 5159 5147 </li> 5160 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">6.1</a>, <a href="#rfc.xref.RFC5322.2">7.10</a>, <a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a>, <a href="#RFC5322"><b>11.2</b></a>, <a href="#rfc.xref.RFC5322.5">D. 6</a><ul>5148 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">6.1</a>, <a href="#rfc.xref.RFC5322.2">7.10</a>, <a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a>, <a href="#RFC5322"><b>11.2</b></a>, <a href="#rfc.xref.RFC5322.5">D.4</a><ul> 5161 5149 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC5322.1">6.1</a></li> 5162 5150 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC5322.3">7.12</a>, <a href="#rfc.xref.RFC5322.4">7.12</a></li> … … 5170 5158 <li><em>RFC5789</em> <a href="#rfc.xref.RFC5789.1">2.3.5</a>, <a href="#RFC5789"><b>11.2</b></a></li> 5171 5159 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>11.2</b></a></li> 5172 <li><em>RFC6151</em> <a href="#RFC6151"><b>11.2</b></a>, <a href="#rfc.xref.RFC6151.1">D. 8</a></li>5173 <li><em>RFC6266</em> <a href="#RFC6266"><b>11.2</b></a>, <a href="#rfc.xref.RFC6266.1">D. 7</a>, <a href="#rfc.xref.RFC6266.2">D.8</a></li>5160 <li><em>RFC6151</em> <a href="#RFC6151"><b>11.2</b></a>, <a href="#rfc.xref.RFC6151.1">D.6</a></li> 5161 <li><em>RFC6266</em> <a href="#RFC6266"><b>11.2</b></a>, <a href="#rfc.xref.RFC6266.1">D.5</a>, <a href="#rfc.xref.RFC6266.2">D.6</a></li> 5174 5162 </ul> 5175 5163 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1645 r1646 3996 3996 </t> 3997 3997 </section> 3998 3999 <section title="Content Coding Registry" anchor="content.coding.registration"> 4000 <t> 4001 The registration procedure for HTTP Content Codings is now defined 4002 by <xref target="content.coding.registry"/> of this document. 4003 </t> 4004 <t> 4005 The HTTP Content Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/> 4006 shall be updated with the registration below: 4007 </t> 4008 <texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table"> 4009 <ttcol>Name</ttcol> 4010 <ttcol>Description</ttcol> 4011 <ttcol>Reference</ttcol> 4012 <c>compress</c> 4013 <c>UNIX "compress" program method</c> 4014 <c> 4015 &compress-coding; 4016 </c> 4017 <c>deflate</c> 4018 <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside 4019 the "zlib" data format (<xref target="RFC1950"/>) 4020 </c> 4021 <c> 4022 &deflate-coding; 4023 </c> 4024 <c>gzip</c> 4025 <c>Same as GNU zip <xref target="RFC1952"/></c> 4026 <c> 4027 &gzip-coding; 4028 </c> 4029 <c>identity</c> 4030 <c>reserved (synonym for "no encoding" in Accept-Encoding header field)</c> 4031 <c> 4032 <xref target="header.accept-encoding"/> 4033 </c> 4034 </texttable> 4035 </section> 4036 3998 4037 </section> 3999 4038 … … 4120 4159 via SMTP, for example. As such, proxies &SHOULD; restrict CONNECT 4121 4160 access to a small number of known ports. 4161 </t> 4162 </section> 4163 4164 <section title="Privacy Issues Connected to Accept Header Fields" anchor="privacy.issues.connected.to.accept.header.fields"> 4165 <t> 4166 Accept header fields can reveal information about the user to all 4167 servers which are accessed. The Accept-Language header field in particular 4168 can reveal information the user would consider to be of a private 4169 nature, because the understanding of particular languages is often 4170 strongly correlated to the membership of a particular ethnic group. 4171 User agents which offer the option to configure the contents of an 4172 Accept-Language header field to be sent in every request are strongly 4173 encouraged to let the configuration process include a message which 4174 makes the user aware of the loss of privacy involved. 4175 </t> 4176 <t> 4177 An approach that limits the loss of privacy would be for a user agent 4178 to omit the sending of Accept-Language header fields by default, and to ask 4179 the user whether or not to start sending Accept-Language header fields to a 4180 server if it detects, by looking for any Vary header fields 4181 generated by the server, that such sending could improve the quality 4182 of service. 4183 </t> 4184 <t> 4185 Elaborate user-customized accept header fields sent in every request, 4186 in particular if these include quality values, can be used by servers 4187 as relatively reliable and long-lived user identifiers. Such user 4188 identifiers would allow content providers to do click-trail tracking, 4189 and would allow collaborating content providers to match cross-server 4190 click-trails or form submissions of individual users. Note that for 4191 many users not behind a proxy, the network address of the host 4192 running the user agent will also serve as a long-lived user 4193 identifier. In environments where proxies are used to enhance 4194 privacy, user agents ought to be conservative in offering accept 4195 header configuration options to end users. As an extreme privacy 4196 measure, proxies could filter the accept header fields in relayed requests. 4197 General purpose user agents which provide a high degree of header 4198 configurability &SHOULD; warn users about the loss of privacy which can 4199 be involved. 4122 4200 </t> 4123 4201 </section> … … 6046 6124 </section> 6047 6125 6048 6049 <section title="IANA Considerations" anchor="IANA.considerations3">6050 6051 <section title="Content Coding Registry" anchor="content.coding.registration">6052 <t>6053 The registration procedure for HTTP Content Codings is now defined6054 by <xref target="content.coding.registry"/> of this document.6055 </t>6056 <t>6057 The HTTP Content Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>6058 shall be updated with the registration below:6059 </t>6060 <texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table">6061 <ttcol>Name</ttcol>6062 <ttcol>Description</ttcol>6063 <ttcol>Reference</ttcol>6064 <c>compress</c>6065 <c>UNIX "compress" program method</c>6066 <c>6067 &compress-coding;6068 </c>6069 <c>deflate</c>6070 <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside6071 the "zlib" data format (<xref target="RFC1950"/>)6072 </c>6073 <c>6074 &deflate-coding;6075 </c>6076 <c>gzip</c>6077 <c>Same as GNU zip <xref target="RFC1952"/></c>6078 <c>6079 &gzip-coding;6080 </c>6081 <c>identity</c>6082 <c>reserved (synonym for "no encoding" in Accept-Encoding header field)</c>6083 <c>6084 <xref target="header.accept-encoding"/>6085 </c>6086 </texttable>6087 </section>6088 6089 </section>6090 6091 <section title="Security Considerations" anchor="security.considerations3">6092 <t>6093 This section is meant to inform application developers, information6094 providers, and users of the security limitations in HTTP/1.1 as6095 described by this document. The discussion does not include6096 definitive solutions to the problems revealed, though it does make6097 some suggestions for reducing security risks.6098 </t>6099 6100 <section title="Privacy Issues Connected to Accept Header Fields" anchor="privacy.issues.connected.to.accept.header.fields">6101 <t>6102 Accept header fields can reveal information about the user to all6103 servers which are accessed. The Accept-Language header field in particular6104 can reveal information the user would consider to be of a private6105 nature, because the understanding of particular languages is often6106 strongly correlated to the membership of a particular ethnic group.6107 User agents which offer the option to configure the contents of an6108 Accept-Language header field to be sent in every request are strongly6109 encouraged to let the configuration process include a message which6110 makes the user aware of the loss of privacy involved.6111 </t>6112 <t>6113 An approach that limits the loss of privacy would be for a user agent6114 to omit the sending of Accept-Language header fields by default, and to ask6115 the user whether or not to start sending Accept-Language header fields to a6116 server if it detects, by looking for any Vary header fields6117 generated by the server, that such sending could improve the quality6118 of service.6119 </t>6120 <t>6121 Elaborate user-customized accept header fields sent in every request,6122 in particular if these include quality values, can be used by servers6123 as relatively reliable and long-lived user identifiers. Such user6124 identifiers would allow content providers to do click-trail tracking,6125 and would allow collaborating content providers to match cross-server6126 click-trails or form submissions of individual users. Note that for6127 many users not behind a proxy, the network address of the host6128 running the user agent will also serve as a long-lived user6129 identifier. In environments where proxies are used to enhance6130 privacy, user agents ought to be conservative in offering accept6131 header configuration options to end users. As an extreme privacy6132 measure, proxies could filter the accept header fields in relayed requests.6133 General purpose user agents which provide a high degree of header6134 configurability &SHOULD; warn users about the loss of privacy which can6135 be involved.6136 </t>6137 </section>6138 6139 </section>6140 6141 6142 6126 <section title="Differences between HTTP and MIME" anchor="differences.between.http.and.mime"> 6143 6127 <t>
Note: See TracChangeset
for help on using the changeset viewer.