You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Claude Montpetit <cl...@montpetit.net> on 2002/04/14 00:54:10 UTC
Corrupted Ouput - Tomcat 4.0.3
There seems to be a bug in the servlet output. I installed two versions
of Tomcat freshly installed on my machine. All I did was change the port
numbers and add 2 image files:
Tomcat 3.2.4: http://24.202.111.74:8081/test.jpg
Tomcat 4.0.3: http://24.202.111.74:8082/test.jpg
(Sorry, images are big (500K) but they make the problem more
reproducible)
The version 4 corrupts the image while version 3 does not. If you try
these links and 4 does not seem to corrupt the image, try refreshing a
couple of times.
This does not happen when I access these images using localhost, or the
local IP address. This only happens when the images are accessed using
my network IP address (24.202.111.74). My machine is running behind a
router that forwards request for ports 8081 and 8082 to my working
machine that hosts these tomcat instances.
At first, I thought it was a router problem but since v3.2.4 works just
fine, I am now leaning toward a problem in Tomcat.
Note that this problem happens also with simple text output. The image
just makes it more obvious.
Environment: Windows 2000
Please let me know if I should have posted this to tomcat-users instead.
PS: These links will not be there for too long...-)
--
Claude Montpetit
claude@montpetit.net
--
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE : Corrupted Ouput - Tomcat 4.0.3
Posted by Claude Montpetit <cl...@montpetit.net>.
I guess you are right. I do not think Tomcat is responsible for this. I
suspect that the reason v3 appears to be fine could be due to a
different output buffer size. I may try to play with this to prove
myself that the problem is in my network (clues on how to change output
buffer size on V3 and V4 would be appreciated). Also, it seems that the
problem only occurs when accessing the web site from inside my network
using the external IP address. When accessing the same IP from the
outside, the problem does not seem to occur (i.e. none of you should see
corrupted images from the links below. But if you do, let me know
please).
Sorry for thinking tomcat was responsible... Shame on me ;-)
Claude
>
> > There seems to be a bug in the servlet output. I installed two
versions
> > of Tomcat freshly installed on my machine. All I did was change the
port
> > numbers and add 2 image files:
> >
> > Tomcat 3.2.4: http://24.202.111.74:8081/test.jpg
> > Tomcat 4.0.3: http://24.202.111.74:8082/test.jpg
>
> Tomcat 4 does not corrupt images, binaries, or anything like that.
This
> has
> been proven on and on by many people using it (like myself) on various
> websites.
> This has actually been proven by your own website, since when I
actually
> tried the second link (I didn't even try the first one) the image came
up
> fine.
>
> There is nothing which Tomcat can do to make the network stack behave
the
> way you say it does.
>
> I assume there is something wrong somewhere in your network
configuration,
> or something like that.
>
> If you still think there is a problem in Tomcat, I'm afaraid I cannot
> reproduce it (and I never experienced it) or help debug it, so you'll
have
> to do the investigation.
>
> Remy
>
>
> --
> To unsubscribe, e-mail: <mailto:tomcat-dev-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-dev-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Corrupted Ouput - Tomcat 4.0.3
Posted by Remy Maucherat <re...@apache.org>.
> There seems to be a bug in the servlet output. I installed two versions
> of Tomcat freshly installed on my machine. All I did was change the port
> numbers and add 2 image files:
>
> Tomcat 3.2.4: http://24.202.111.74:8081/test.jpg
> Tomcat 4.0.3: http://24.202.111.74:8082/test.jpg
Tomcat 4 does not corrupt images, binaries, or anything like that. This has
been proven on and on by many people using it (like myself) on various
websites.
This has actually been proven by your own website, since when I actually
tried the second link (I didn't even try the first one) the image came up
fine.
There is nothing which Tomcat can do to make the network stack behave the
way you say it does.
I assume there is something wrong somewhere in your network configuration,
or something like that.
If you still think there is a problem in Tomcat, I'm afaraid I cannot
reproduce it (and I never experienced it) or help debug it, so you'll have
to do the investigation.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE : Corrupted Ouput - Tomcat 4.0.3
Posted by Claude Montpetit <cl...@montpetit.net>.
One important thing: to refresh an image
- in IE, you have to hold the <CTRL> key: <CTRL>F5, or <CTRL>click
- in Netscape, you have to hold the <SHIFT> key: <SHIFT>click
Otherwise, the browsers use the cached image.
(I saw the need to send this after looking at the access logs... ;-)
Claude
-----Message d'origine-----
De : Claude Montpetit [mailto:claude@montpetit.net]
Envoyé : 13 avril, 2002 18:54
À : tomcat-dev@jakarta.apache.org
Objet : Corrupted Ouput - Tomcat 4.0.3
There seems to be a bug in the servlet output. I installed two versions
of Tomcat freshly installed on my machine. All I did was change the port
numbers and add 2 image files:
Tomcat 3.2.4: http://24.202.111.74:8081/test.jpg
Tomcat 4.0.3: http://24.202.111.74:8082/test.jpg
(Sorry, images are big (500K) but they make the problem more
reproducible)
The version 4 corrupts the image while version 3 does not. If you try
these links and 4 does not seem to corrupt the image, try refreshing a
couple of times.
This does not happen when I access these images using localhost, or the
local IP address. This only happens when the images are accessed using
my network IP address (24.202.111.74). My machine is running behind a
router that forwards request for ports 8081 and 8082 to my working
machine that hosts these tomcat instances.
At first, I thought it was a router problem but since v3.2.4 works just
fine, I am now leaning toward a problem in Tomcat.
Note that this problem happens also with simple text output. The image
just makes it more obvious.
Environment: Windows 2000
Please let me know if I should have posted this to tomcat-users instead.
PS: These links will not be there for too long...-)
--
Claude Montpetit
claude@montpetit.net
--
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>