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- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:tomcat-dev- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
