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/06/17 18:05:31 UTC

DO NOT REPLY [Bug 9361] - jsp:param calls URLEncoder.encode() without null check

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

jsp:param calls URLEncoder.encode() without null check





------- Additional Comments From jessh@ptc.com  2002-06-17 16:05 -------
A resolution on this issue is quite important.  If this is not a bug per se, it 
would seem highly desirable to allow null's in this situation anyway as 
previous versions of Tomcat and other major servlet engines (e.g. JRun, 
iPlanet) do null throw exceptions upon passing null values to jsp:param.

Also, is use of URLEncoder.encode() really the best tactic considering that it 
does not handle non-ASCII characters?  Should the characters first be UTF-8 
encoded and then URL encoded to handle this?

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