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 16335] New: - Setting Jasper logging level to DEBUG causes request.setCharacterencoding() to be ignored
Date Wed, 22 Jan 2003 16:25:41 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=16335>.
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=16335

Setting Jasper logging level to DEBUG causes request.setCharacterencoding() to be ignored

           Summary: Setting Jasper logging level to DEBUG causes
                    request.setCharacterencoding() to be ignored
           Product: Tomcat 4
           Version: 4.1.18
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: francis.vermeulen@atosorigin.com


If the Jasper logging level is set to DEBUG, the JspServlet service() method 
logs the request parameters by calling request.getParameter() for each 
parameter, without specifying any encoding (which it can't of course, not 
knowing that...)

When a JSP page wants to get a parameter afterwards by explicitely specifying 
an encoding (by means of the request.setCharacterEncoding()) method, the 
HttpRequestBase simply returns the result of the first call by Jasper and hence 
the specified encoding is ignored.

As far as I'm concerned, causing software to print debug information should 
NEVER alter its behaviour, hence I consider this to be a bug.

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


Mime
View raw message