- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Fri, 2 Nov 2007 19:47:28 -0700
- To: HTTP Working Group <ietf-http-wg@w3.org>
The last part of the proposed solution for [i16] should be
<section title="No Content-Transfer-Encoding" anchor="no.content-
transfer-encoding">
<t>
- HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC
+ HTTP does not use the Content-Transfer-Encoding field of RFC
2045. Proxies and gateways from MIME-compliant protocols to HTTP
&MUST;
- remove any non-identity CTE ("quoted-printable" or "base64")
encoding
+ remove any Content-Transfer-Encoding
prior to delivering the response message to an HTTP client.
</t>
because there is absolutely no reason to abbreviate the field name
when it is only used twice in the entire document.
....Roy
Received on Saturday, 3 November 2007 02:47:26 UTC