-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
André Warnier wrote: > I am using a Tomcat java application which unfortunately sets the > Content-Type response header wrongly : it says "text/html; > charset=iso-8859-1" instead of "text/html; charset=iso-8859-2", and > there is no way I can change that application itself. > So I am trying to rectify that header after-the-fact, using mod_headers. > Unfortunately, it does not seem to work. This obviously isn't answering your question, but isn't the application advertising ISO-8859-2 as the content type because that's what it's using? If the application can't be changed (that is, the Content-Type is set in stone somewhere) wouldn't the /actual/ encoding being used also be set in stone? What's the danger in allowing the application to simply continue to use ISO-8859-1 (other than the obvious limitations of the character set itself)? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklr5I0ACgkQ9CaO5/Lv0PCt9QCfQivKj8se2vGgYt8ayOGGroMs i6sAn1UHLVPMGZXmPd+qiE3XD6ECRTgk =JhD5 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
