Enable (comment in) the AccessLogValve in your server.xml. That way you
will be able to see exactly what requested URLs result in 404s.
The file is enabled and nope -- I'm not seeing any 404 errors.
Yoav Shapira http://www.yoavshapira.com
What confuses me is why I get a ClassCastException? This m
Hi,
Because this processing servlet of yours itself had an error. A JSP
file by default is processed by Tomcat's JSP servlet, not your Router
servlet. Accordingly, it's not subject to your custom error handling
mechanism. A more standard way to do this is declare an
for 404's in your web.xml, a
Hi,
>Sorry, not sure I understand this. Is this not what I've done with
this?:
>
>404
>/404.html
>
Yeah, that is what you've done. I didn't read your original web.xml
carefully enough it seems ;)
>My understanding of how this works is that any URL that ends with
in your web.xml, and/or an errorPage for the specific JSP page
in the JSP page itself.
Yoav Shapira http://www.yoavshapira.com
>-Original Message-
>From: Jon Doe [mailto:[EMAIL PROTECTED]
>Sent: Sunday, December 12, 2004 7:58 PM
>To: [EMAIL PROTECTED]
>Subject: Query with
Can someone please explain why I get the default Tomcat 404 error when a
pages does not exist?
I have a set of URLs that end with *.ext. These are all routed to a servlet
called Router, and these all work fine. This servlet has catch-all at the
end that displays an error message when an unknown
