> Remy Maucherat wrote:
> >
> > > There seems to be a bug in the servlet output.
> >
> > 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.
> >
>
> That logic doesn't work. The fact t
Remy Maucherat wrote:
>
> > There seems to be a bug in the servlet output.
>
> 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.
>
That logic doesn't work. The fact that it works for
s
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
> 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
One important thing: to refresh an image
- in IE, you have to hold the key: F5, or click
- in Netscape, you have to hold the key: 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---
