Re: default charset broken

On Sun, 8 Jun 2003, Martin Duerst wrote:

> That's because in RFC 2068, and even still in RFC 2616, there
> is some language about user agents that get completely confused
> if they see a 'charset' parameter in a Content-Type: header.
> As far as I remember, that was Netscape 2 and friends.

It's actually just Netscape 1.0 (and earlier) and NCSA Mosaic.  Netscape
1.1 and up handle the charset parameter fine.

-- 
Liam Quinn