I've found that the error-page handling seems to work on the first visit, but then fails on alternating visits from the client if using Mozilla/Netscape. If I use Internet Explorer, it seems to work the first time and fail every time after.
For an example, I have the following access log info: ... 192.168.1.### - - [21/Jun/2002:20:24:26 -0500] "GET /errordemo/mister_e/ HTTP/1.1" 200 124 192.168.1.### - - [21/Jun/2002:20:24:28 -0500] "GET /errordemo/mister_e/ HTTP/1.1" 500 - 192.168.1.### - - [21/Jun/2002:20:24:29 -0500] "GET /errordemo/mister_e/ HTTP/1.1" 200 124 192.168.1.### - - [21/Jun/2002:20:24:31 -0500] "GET /errordemo/mister_e/ HTTP/1.1" 500 - ... In this case, Mozilla was connecting to the Tomcat, hence the alternating responses. I've tried to no avail in adjusting cache settings, but they don't make a difference with the browsers. Why would Tomcat sometimes return the error-page, but not for all subsequent retries? Is this a config issue? A bug in Tomcat? Or, is it ... *gasp* ... expected behavior? :) James -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
