-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joe,
Joseph S wrote: > Christopher Schultz wrote: > >> Setting the encoding of the response is sometimes necessary when the >> browser (stupidly, IMO) elects not to send the charset being used to the >> server. >> > It isn't the browser's fault, its the spec's fault. See > https://bugzilla.mozilla.org/show_bug.cgi?id=289060#c8 Certainly, the specification doesn't help in this regard. I'm disappointed that things like this never get fixed in specifications. This question comes up all the time, and the solution is almost always to simply pick a charset and use it all the time, without question. But that's messy, and doesn't allow the client to make any choices about character encoding, etc. :( - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGxbRM9CaO5/Lv0PARAuqDAJ9rbnlgMeJe5NjCLyWzj1S53EAxHgCdExsx CYVYrMDRFMhDpxUoXMFRpPg= =lW9w -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
