W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Re: #243: iso-8859-1 in C-D

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Sun, 07 Nov 2010 02:53:29 +0100
To: Mark Nottingham <mnot@mnot.net>
Cc: httpbis Group <ietf-http-wg@w3.org>
Message-ID: <6l0cd699516rpisfmjlc146ncob93iio5i@hive.bjoern.hoehrmann.de>
* Mark Nottingham wrote:
>According to <http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-12#section-3.2>:
>>    Historically, HTTP has allowed field content with text in the ISO-
>>    8859-1 [ISO-8859-1] character encoding and supported other character
>>    sets only through use of [RFC2047] encoding.  In practice, most HTTP
>>    header field values use only a subset of the US-ASCII character
>>    encoding [USASCII].  Newly defined header fields SHOULD limit their
>>    field values to US-ASCII characters.  Recipients SHOULD treat other
>>    (obs-text) octets in field content as opaque data.
>I don't see what not specifying the character set that doesn't require encoding buys us here. 

I think this issue can be closed; I think the document has been changed
to my satisfaction. (I do note that there is some slight inaccuracy in
the text you cite and the Content-Disposition draft: if the filename
value is a `token` instead of a quoted string, RFC 2616 does not define
the encoding of the token to be ISO-8859-1; the ISO-8859-1 language is
for words of TEXT, which are in comments in quoted strings only.)
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Sunday, 7 November 2010 01:54:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:55 UTC