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 45065] RequestDispatcher restricts access to ApplicationHttpRequest
Date Tue, 27 May 2008 18:10:26 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065


Paul Copeland <tech@jotobjects.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tech@jotobjects.com




--- Comment #3 from Paul Copeland <tech@jotobjects.com>  2008-05-27 11:10:26 PST ---
I found a workaround that does not use reflection in this part of the
application.

The suggested solution requires that you already know the class implements the
HttpServletRequest interface, in which case there is no point in using
reflection to invoke the method. The example code was just to demonstrate the
problem with the simplest case - the problem occurred in a generic reflection
routine. Theoretically you might be able to check all the interfaces
implemented and find one that allows you to invoke the target method. In
practice that might be a performance issue.

Just some guesses - Is the wrapper attempting to handle the case of forwarding
to another context which is optionally allowed if the container supports it? 
Hopefully this problem does not occur in filter chains but I have not tried
that.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


Mime
View raw message