On Sat, Jan 29, 2005 at 01:53:58AM -0500, Neil Schemenauer wrote:
> Unfortunately, leaving the default for set_content_type() be
> 'iso-8859-1' would also be surprising.  I guess another option
> would be to set self.charset set None if no charset was supplied
> to set_content_type().  In that case, the charset parameter of the
> Content-Type header would be left out.

After reading RFC 2616, I think leaving the default for
set_content_type() to 'iso-8859-1' is correct.  Leaving out the
charset parameter will cause the client to interpret the response as
'iso-8859-1' anyhow.  Buggy clients may try to guess if the charset
is not specified so it is better to specify it.

  Neil