On Fri, May 20, 2005 at 09:21:14PM +0200, Damjan wrote:
> ?? If the content is non-text, there should be no charset at all.
> not even a default one.
Hmm, I think you may be right. Section 3.7.1 from RFC 2616:
The "charset" parameter is used with some media types to define
the character set (section 3.4) of the data. When no explicit
charset parameter is provided by the sender, media subtypes of
the "text" type are defined to have a default charset value of
"ISO-8859-1" when received via HTTP. Data in character sets
other than "ISO-8859-1" or its subsets MUST be labeled with an
appropriate charset value.
I had originally thought that all types default to iso-8859-1 if the
charset is not specified. I see now that the default only applies
when the type is text/*. I wonder if it should be possible to to
set HTTPResponse.charset to None.
Neil
_______________________________________________
Quixote-users mailing list
[email protected]
http://mail.mems-exchange.org/mailman/listinfo/quixote-users
