Shapira, Yoav wrote:
Hi,
When you get a chance, please read
http://www.river.com/users/share/etiquette/#quotes -- it's helpful and
appreciated on this list ;)
I'm sorry; I'm following several mailing lists, and the etiquette
expected varies slightly. I will keep this in mind ;)
/Eirik
--
Hi again,
Shapira, Yoav wrote:
Hi,
>After upgrading from tomcat 4.1 to 5.0, a critical application here has
It'd be a shame if the upgrade wasn't tested first in a test/QA
environment ;(
>In 5.0.29, this comes out as
>
>Content-Type: application/xml;charset=utf-8
It's also interesting that you
Hi again,
Shapira, Yoav wrote:
Hi,
Well that's the thing.. It was tested, worked, but then the "other end"
changed their stuff in a way that turned out to be incompatible. In any
Gotta love it ;)
I was actually of the impression that 5.0.29 was *not* a beta release;
possibly because it is the on
Shapira, Yoav wrote:
Hi,
After upgrading from tomcat 4.1 to 5.0, a critical application here has
It'd be a shame if the upgrade wasn't tested first in a test/QA
environment ;(
Well that's the thing.. It was tested, worked, but then the "other end"
changed their stuff in a way that turned out to
Hi,
Follow-up: The same happens when using Tomcat stand-alone - i.e. no
Apache and no jk.
/Eirik
Eirik Øverby wrote:
Hi,
no, it is not related at all to the oft-discussed UTF-8 issues.
This simply has to do with how the connector splits up the Content-Type
string and then sews it together
support (using different
charsets - Chinese or Japanese) on jsp page and would break (not displaying the
non-english characters) on tomcat 5.0.29.
Arnab
-Original Message-
From: Eirik Øverby [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 01, 2004 11:15 PM
To: [EMAIL PROTECTED
Hi,
After upgrading from tomcat 4.1 to 5.0, a critical application here has
stopped working as expected. Upon replying to incoming requests, it
would usually spit out the following - just like the servlet says:
Content-Type: application/xml; charset=utf-8
In 5.0.29, this comes out as
Content-Type: