Changeset 911 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 24/07/10 09:23:44 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r901 r911 4884 4884 </section> 4885 4885 4886 <section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">4887 <t>4888 This specification has been carefully audited to correct and4889 disambiguate key word usage; RFC 2068 had many problems in respect to4890 the conventions laid out in <xref target="RFC2119"/>.4891 </t>4892 <t>4893 Transfer-coding and message lengths all interact in ways that4894 required fixing exactly when chunked encoding is used (to allow for4895 transfer encoding that might not be self delimiting); it was important4896 to straighten out exactly how message lengths are computed. (Sections4897 <xref target="transfer.codings" format="counter"/>, <xref target="message.body" format="counter"/>,4898 <xref target="header.content-length" format="counter"/>,4899 see also <xref target="Part5"/>)4900 </t>4901 <t>4902 The use and interpretation of HTTP version numbers has been clarified4903 by <xref target="RFC2145"/>. Require proxies to upgrade requests to highest protocol4904 version they support to deal with problems discovered in HTTP/1.04905 implementations (<xref target="http.version"/>)4906 </t>4907 <t>4908 Quality Values of zero should indicate that "I don't want something"4909 to allow clients to refuse a representation. (<xref target="quality.values"/>)4910 </t>4911 <t>4912 Transfer-coding had significant problems, particularly with4913 interactions with chunked encoding. The solution is that transfer-codings4914 become as full fledged as content-codings. This involves4915 adding an IANA registry for transfer-codings (separate from content4916 codings), a new header field (TE) and enabling trailer headers in the4917 future. Transfer encoding is a major performance benefit, so it was4918 worth fixing <xref target="Nie1997"/>. TE also solves another, obscure, downward4919 interoperability problem that could have occurred due to interactions4920 between authentication trailers, chunked encoding and HTTP/1.04921 clients.(Section4922 <xref target="transfer.codings" format="counter"/>,4923 <xref target="chunked.encoding" format="counter"/>,4924 <xref target="non-modifiable.headers" format="counter"/>,4925 and <xref target="header.te" format="counter"/>)4926 </t>4927 <t>4928 Proxies should be able to add Content-Length when appropriate.4929 (<xref target="non-modifiable.headers"/>)4930 </t>4931 </section>4932 4933 4886 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616"> 4934 4887 <t> … … 5716 5669 "HTTP(s) URI scheme definitions" 5717 5670 </t> 5671 <t> 5672 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>: 5673 "consider removing the 'changes from 2068' sections" 5674 </t> 5718 5675 </list> 5719 5676 </t>
Note: See TracChangeset
for help on using the changeset viewer.