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 24940] New: - Direct access to request wrapped in (Http)ServletWrapper
Date Mon, 24 Nov 2003 12:47:58 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=24940>.
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=24940

Direct access to request wrapped in (Http)ServletWrapper

           Summary: Direct access to request wrapped in (Http)ServletWrapper
           Product: Tomcat 5
           Version: 5.0.14
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: Paul.Harvey@fdisolutions.com


The ServletWrapper class provides getRequest and setRequest methods - as 
specificied in Java™ Servlet Specification Version 2.4 Final Draft.

These methods are used in core of Tomcat to directly access the wrapped 
request and hence to bipass the wrapper.  The whole point of the wrapper is to 
do just that - to wrap the request,  so all access to the wrapped object 
should go through the wrapper implementation - this allows it to control and 
to modify access to the request as it sees fit.  

It would seem best to me to remove the getRequest and setRequest methods 
altogether in order to force access through the Wrapper (of course this would 
mean altering the 2.4 spec. doc also).

This is not just a theoretical design problem it has manifested as a bug in my 
code.

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


Mime
View raw message