tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5599] - StackOverflowError
Date Thu, 03 Jan 2002 01:19:35 GMT
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=5599>.
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=5599

StackOverflowError

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From craig.mcclanahan@sun.com  2002-01-02 17:19 -------
This is a user error, and Tomcat cannot do anything to stop it.

When you use a URL mapping of "/*", that means you want this servlet to be 
responsible for ALL requests for the web application (even JSP pages).  So, the 
RequestDispatcher you create will therefore cause the same servlet to be invoked 
again, which will do the same thing again, and so on.

If you want to "protect the contents of a directory", you should use a *Filter* 
mapped to "/*" rather than a *Servlet*.  This doesn't interfere with the actual 
processing performed by your servlets and JSP pages, but does give you the 
opportunity to intercept things.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message