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 3665] - Request Dispatching - Parameters are not properly set
Date Tue, 18 Sep 2001 00:02:02 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=3665>.
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=3665

tom.sprenger@adnovum.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Minor



------- Additional Comments From tom.sprenger@adnovum.com  2001-09-17 17:02 -------
The reported bug can be reduced to the case where the getInfoPath() of the
called servlet is empty ('null'). In this case the field
javax.servlet.include.path_info will not be set. All other fields are present in
the request attributes. This behavior might be a consequence of the
specification refinement of the "Dispatching Reuqests" section.

Although a call like req.getAttribute("javax.servlet.include.path_info") would
return the correct result (namely 'null'), the question still to be discussed is
if it is appropriate to map an empty pathInfo to a RequestAttribute by just not
setting it? It might be functionally correct, but what the implementation
concerns not very clean.

Mime
View raw message