You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/07/31 18:50:10 UTC

DO NOT REPLY [Bug 11335] New: - RequestDispatcher.forward() is not 2.3 spec compliant

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=11335>.
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=11335

RequestDispatcher.forward() is not 2.3 spec compliant

           Summary: RequestDispatcher.forward() is not 2.3 spec compliant
           Product: Tomcat 4
           Version: 4.0.4 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: gregw@mortbay.org


In SRV.8.4 of the servlet spec it says:

 "The path elements of the request object exposed to the target servlet must   
  reflect the path used to obtain the RequestDispatcher. The only exception to 
  this is if the RequestDispatcher was obtained via the getNamedDispatcher 
  method."

With tomcat 4, if the request passed to forward has been wrapped
(either by the current servlet/filter or by a previous servlet/filter) and that 
wrapper changes the value of the path methods - then the forward method exposes
the wrapped values rather than the values used to obtain the request 
dispatcher.

The Jetty container wraps the forwarded request and re-implements the path
methods so that the correct values are exposed.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>