Tomcat 3.3 looks like it has the same problem, only worse (since it will fail a static jsp:include that lives in WEB-INF). However, the check isn't really needed in 3.3, since if the request came from the user AccessInterceptor would have already failed it. If nobody objects, I'll remove the check from StaticInterceptor later in the week. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 1:49 PM Subject: DO NOT REPLY [Bug 5724] - Error page not displaying
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG > RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT > <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5724>. > ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND > INSERTED IN THE BUG DATABASE. > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5724 > > Error page not displaying > > [EMAIL PROTECTED] changed: > > What |Removed |Added > -------------------------------------------------------------------------- -- > Status|RESOLVED |REOPENED > Resolution|INVALID | > > > > ------- Additional Comments From [EMAIL PROTECTED] 2002-01-07 13:49 ------- > I can't find it either, so it looks like it would be allowed. The error is > thrown by the DefaultServlet, which will refuse to return any page from > /WEB-INF. Removing the check is very risky for obvious reasons, so I think we'll > delay a fix. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
