Issue updated. On 03/11/2007, at 1:47 PM, Roy T. Fielding wrote: > > 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 > -- Mark Nottingham http://www.mnot.net/Received on Monday, 12 November 2007 09:45:36 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 6 June 2008 08:04:33 GMT