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,
When you get a chance, please read
http://www.river.com/users/share/etiquette/#quotes -- it's helpful and
appreciated on this list ;)
Until now I have simply placed the tomcat-coyote.jar file into
server/lib; this has worked fine. However, when following your
suggestion (placing the modified
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
On Thu, Dec 02, 2004 at 03:26:39PM +0100, Eirik ?verby wrote:
: 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,
Does it have anything to do with UTF-8 encoding 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:
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 without adding a space after the ;.
/Eirik
Arnab Chakravarty wrote:
Eirik,
Does it have anything to do with UTF-8 encoding
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
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 chose a beta version of Tomcat,
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,
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 only current version available in
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
Hi,
Anything I can do to increase the probability of this happening? Like,
filing a bug report or feature request or whatever it should be called?
Note that this also happens if you run Tomcat as a standalone
HTTP/HTTPS
server..
You can file a bug report which would decrease the probability of
12 matches
Mail list logo
