Changeset 1742
- Timestamp:
- 08/07/12 19:20:40 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1741 r1742 710 710 <li>A.1.1 <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Multi-homed Web Servers</a></li> 711 711 <li>A.1.2 <a href="#compatibility.with.http.1.0.persistent.connections">Keep-Alive Connections</a></li> 712 <li>A.1.3 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 712 713 </ul> 713 714 </li> … … 2958 2959 is being used. 2959 2960 </p> 2961 <h3 id="rfc.section.A.1.3"><a href="#rfc.section.A.1.3">A.1.3</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3> 2962 <p id="rfc.section.A.1.3.p.1">HTTP/1.1 introduces the <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.4" title="Transfer-Encoding">Section 3.3.1</a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 2963 </p> 2960 2964 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 2961 2965 <p id="rfc.section.A.2.p.1">Clarify that the string "HTTP" in the HTTP-version ABFN production is case sensitive. Restrict the version numbers to be single … … 3682 3686 <li>TE <a href="#rfc.xref.header.te.1">4</a>, <a href="#rfc.xref.header.te.2">4.1</a>, <a href="#rfc.iref.h.8"><b>4.3</b></a>, <a href="#rfc.xref.header.te.3">4.3.1</a>, <a href="#rfc.xref.header.te.4">7.1</a></li> 3683 3687 <li>Trailer <a href="#rfc.xref.header.trailer.1">4.1</a>, <a href="#rfc.iref.h.9"><b>4.4</b></a>, <a href="#rfc.xref.header.trailer.2">7.1</a></li> 3684 <li>Transfer-Encoding <a href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a href="#rfc.iref.h.6"><b>3.3.1</b></a>, <a href="#rfc.xref.header.transfer-encoding.2">4</a>, <a href="#rfc.xref.header.transfer-encoding.3">7.1</a> </li>3688 <li>Transfer-Encoding <a href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a href="#rfc.iref.h.6"><b>3.3.1</b></a>, <a href="#rfc.xref.header.transfer-encoding.2">4</a>, <a href="#rfc.xref.header.transfer-encoding.3">7.1</a>, <a href="#rfc.xref.header.transfer-encoding.4">A.1.3</a></li> 3685 3689 <li>Upgrade <a href="#rfc.iref.h.14"><b>6.5</b></a>, <a href="#rfc.xref.header.upgrade.1">7.1</a>, <a href="#rfc.xref.header.upgrade.2">A.2</a></li> 3686 3690 <li>Via <a href="#rfc.xref.header.via.1">2.3</a>, <a href="#rfc.iref.h.13"><b>6.2</b></a>, <a href="#rfc.xref.header.via.2">7.1</a></li> … … 3859 3863 <li><em>Tou1998</em> <a href="#rfc.xref.Tou1998.1">6.3.1</a>, <a href="#Tou1998"><b>10.2</b></a></li> 3860 3864 <li>Trailer header field <a href="#rfc.xref.header.trailer.1">4.1</a>, <a href="#rfc.iref.t.6"><b>4.4</b></a>, <a href="#rfc.xref.header.trailer.2">7.1</a></li> 3861 <li>Transfer-Encoding header field <a href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a href="#rfc.iref.t.4"><b>3.3.1</b></a>, <a href="#rfc.xref.header.transfer-encoding.2">4</a>, <a href="#rfc.xref.header.transfer-encoding.3">7.1</a> </li>3865 <li>Transfer-Encoding header field <a href="#rfc.xref.header.transfer-encoding.1">3.3</a>, <a href="#rfc.iref.t.4"><b>3.3.1</b></a>, <a href="#rfc.xref.header.transfer-encoding.2">4</a>, <a href="#rfc.xref.header.transfer-encoding.3">7.1</a>, <a href="#rfc.xref.header.transfer-encoding.4">A.1.3</a></li> 3862 3866 <li>transforming proxy <a href="#rfc.iref.t.1"><b>2.3</b></a></li> 3863 3867 <li>transparent proxy <a href="#rfc.iref.t.3"><b>2.3</b></a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1741 r1742 4936 4936 </t> 4937 4937 </section> 4938 4939 <section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding"> 4940 <t> 4941 HTTP/1.1 introduces the <x:ref>Transfer-Encoding</x:ref> header field 4942 (<xref target="header.transfer-encoding"/>). Proxies/gateways &MUST; remove 4943 any transfer-coding prior to forwarding a message via a MIME-compliant 4944 protocol. 4945 </t> 4946 </section> 4947 4938 4948 </section> 4939 4949 -
draft-ietf-httpbis/latest/p2-semantics.html
r1741 r1742 760 760 <li>A.4 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 761 761 <li>A.5 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 762 <li>A.6 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 763 <li>A.7 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 762 <li>A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 764 763 </ul> 765 764 </li> … … 3924 3923 the destination protocol. 3925 3924 </p> 3926 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 3927 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> 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. 3928 </p> 3929 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> 3930 <p id="rfc.section.A.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 3925 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> 3926 <p id="rfc.section.A.6.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 3931 3927 fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations 3932 3928 and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 5.5.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. … … 3978 3974 <p id="rfc.section.C.p.15">Allow <a href="#header.referer" class="smpl">Referer</a> field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.15</a>) 3979 3975 </p> 3980 <p id="rfc.section.C.p.16">In the description of the <a href="#header.server" class="smpl">Server</a> header field, the <a href="p1-messaging.html#header.via" class="smpl">Via</a> field was described as a SHOULD. The requirement was and is stated 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. 60"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.17</a>)3976 <p id="rfc.section.C.p.16">In the description of the <a href="#header.server" class="smpl">Server</a> header field, the <a href="p1-messaging.html#header.via" class="smpl">Via</a> field was described as a SHOULD. The requirement was and is stated 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.59"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.17</a>) 3981 3977 </p> 3982 3978 <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 5.3</a>) … … 4951 4947 </li> 4952 4948 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 4953 <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">1.3.2</a>, <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.7</a>, <a href="#rfc.xref.Part1.22">2.3.8</a>, <a href="#rfc.xref.Part1.23">3</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.1</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.4.4</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.36">4.6.15</a>, <a href="#rfc.xref.Part1.37">4.7.6</a>, <a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.40">5.4</a>, <a href="#rfc.xref.Part1.41">5.4.1</a>, <a href="#rfc.xref.Part1.42">5.4.1</a>, <a href="#rfc.xref.Part1.43">6.1</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.47">8.1</a>, <a href="#rfc.xref.Part1.48">9.1</a>, <a href="#rfc.xref.Part1.49">9.3</a>, <a href="#rfc.xref.Part1.50">9.8</a>, <a href="#rfc.xref.Part1.51">9.11</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.53">9.17</a>, <a href="#rfc.xref.Part1.54">9.18</a>, <a href="#rfc.xref.Part1.55">10.4</a>, <a href="#rfc.xref.Part1.56">10.4</a>, <a href="#rfc.xref.Part1.57">10.4</a>, <a href="#rfc.xref.Part1.58">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.59"> A.6</a>, <a href="#rfc.xref.Part1.60">C</a><ul>4949 <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">1.3.2</a>, <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.7</a>, <a href="#rfc.xref.Part1.22">2.3.8</a>, <a href="#rfc.xref.Part1.23">3</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.1</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.4.4</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.36">4.6.15</a>, <a href="#rfc.xref.Part1.37">4.7.6</a>, <a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.40">5.4</a>, <a href="#rfc.xref.Part1.41">5.4.1</a>, <a href="#rfc.xref.Part1.42">5.4.1</a>, <a href="#rfc.xref.Part1.43">6.1</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.47">8.1</a>, <a href="#rfc.xref.Part1.48">9.1</a>, <a href="#rfc.xref.Part1.49">9.3</a>, <a href="#rfc.xref.Part1.50">9.8</a>, <a href="#rfc.xref.Part1.51">9.11</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.53">9.17</a>, <a href="#rfc.xref.Part1.54">9.18</a>, <a href="#rfc.xref.Part1.55">10.4</a>, <a href="#rfc.xref.Part1.56">10.4</a>, <a href="#rfc.xref.Part1.57">10.4</a>, <a href="#rfc.xref.Part1.58">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.59">C</a><ul> 4954 4950 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.3</a></li> 4955 4951 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.2</a></li> … … 4962 4958 <li><em>Section 3.2.5</em> <a href="#rfc.xref.Part1.24">3.1</a></li> 4963 4959 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a></li> 4964 <li><em>Section 3.3.1</em> <a href="#rfc.xref.Part1.59">A.6</a></li>4965 4960 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.43">6.1</a></li> 4966 4961 <li><em>Section 4</em> <a href="#rfc.xref.Part1.41">5.4.1</a></li> … … 4976 4971 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.50">9.8</a></li> 4977 4972 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.27">3.1</a></li> 4978 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.53">9.17</a>, <a href="#rfc.xref.Part1. 60">C</a></li>4973 <li><em>Section 6.2</em> <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.53">9.17</a>, <a href="#rfc.xref.Part1.59">C</a></li> 4979 4974 <li><em>Section 6.4.3</em> <a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.51">9.11</a></li> 4980 4975 <li><em>Section 6.5</em> <a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.36">4.6.15</a></li> … … 5067 5062 <li><em>RFC2295</em> <a href="#rfc.xref.RFC2295.1">8</a>, <a href="#RFC2295"><b>13.2</b></a></li> 5068 5063 <li><em>RFC2388</em> <a href="#rfc.xref.RFC2388.1">5.5.2</a>, <a href="#RFC2388"><b>13.2</b></a></li> 5069 <li><em>RFC2557</em> <a href="#rfc.xref.RFC2557.1">9.8</a>, <a href="#RFC2557"><b>13.2</b></a>, <a href="#rfc.xref.RFC2557.2">A. 7</a><ul>5064 <li><em>RFC2557</em> <a href="#rfc.xref.RFC2557.1">9.8</a>, <a href="#RFC2557"><b>13.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.6</a><ul> 5070 5065 <li><em>Section 4</em> <a href="#rfc.xref.RFC2557.1">9.8</a></li> 5071 5066 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1741 r1742 5446 5446 </section> 5447 5447 5448 <section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">5449 <t>5450 HTTP/1.1 introduces the <x:ref>Transfer-Encoding</x:ref> header field5451 (&header-transfer-encoding;). Proxies/gateways &MUST; remove any5452 transfer-coding prior to forwarding a message via a MIME-compliant protocol.5453 </t>5454 </section>5455 5456 5448 <section title="MHTML and Line Length Limitations" anchor="mhtml.line.length"> 5457 5449 <t>
Note: See TracChangeset
for help on using the changeset viewer.