-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Willem,
Willem Moors wrote: > I studied the Response Headers for the ajax call that generates the output > and found that for the correct result (ie. in TC55), the content type was > this: > Content-Type text/plain;charset=ISO-8859-1 > > while for the wrong result (ie. in TC6), the content type was: > Content-Type text/plain Looks like the server is using something else (UTF-8?) in TC 6 and not reporting it to the client. The client is assuming ISO-8859-1 and therefore misinterpreting those characters outside of US-ASCII (such as £). > So would this be the right conclusion : it's TC55 that's wrong here and not > TC 6 ? > TC55 slaps on the 'charset=ISO-8859-1' by default and TC 6 doesn't. It might not be by default: lots of folks explicitly set their charsets to UTF-8 using some other technique. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjJS3sACgkQ9CaO5/Lv0PDsoQCfXcxM6uOoaA7lWCbySN8dNblG u0oAn0ybnK1s5T6TVZuhHemLHnoriQkr =tDJb -----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]
