W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: Factoring out Content-Disposition (i123)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 16 Aug 2008 10:00:35 +0200
Message-ID: <48A68923.9060809@gmx.de>
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
CC: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, ietf-http-wg@w3.org

William A. Rowe, Jr. wrote:
> I'm becoming very confused.  RFC 2616 is very explicit;
> 
>    The TEXT rule is only used for descriptive field contents and values
>    that are not intended to be interpreted by the message parser. Words
>    of *TEXT MAY contain characters from character sets other than ISO-
>    8859-1 [22] only when encoded according to the rules of RFC 2047
>    [14].
> 
>        TEXT           = <any OCTET except CTLs,
>                         but including LWS>
> 
> So, we have a clear definition of where and when and how non-8859-1
> characters are permitted, in spite of your's and Julian's claims in his
> recent draft.  I really wish people would be more accurate in their
> assertions.

I recommend that you look at the mailing list discussions for recent 
discussions about which headers actually *do* use TEXT. See 
<http://tools.ietf.org/wg/httpbis/trac/ticket/111> and 
<http://greenbytes.de/tech/httpbis/issue-111.xhtml>.

BR, Julian
Received on Saturday, 16 August 2008 08:01:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:54 GMT