DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=25965>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=25965 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2005-01-04 18:55 ------- This appears to be a Tomcat bug. AController (the servlet in application A) obtains a context to application B. If Tomcat does not allow this for security reasons, it should return null here (as per the API). If Tomcat returns a context, then this context should be the application context for application B, the same one that we will deal with if the user directly posted to application B. When a request dispatcher is obtained from this new context, we are dealing entirely with resources in context B (the fact that the request originated from application A is irrelevent at this point since we are dealing with a new context). Hence, if test.jsp exists in application B, Tomcat should find it. If Tomcat instead looks for test.jsp in application A, it is incorrect since Tomcat is crossing boundaries (from B to A) that is shouldn't because as I mentioned before we are working with the application context for application B. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
