DO NOT REPLY [Bug 30368] - Problem with URLDecode

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30368>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30368

Problem with URLDecode





------- Additional Comments From ms@docware.de  2004-08-10 07:56 -------
Mark thanks for your reply.
My expected behaviour was (and still is) that the servlet container should make 
no assumption about an encoding of the URI. getPathInfo() should URLdecode the %
xx characters but nothing else. The further interpretation should be in the 
responsibility of my servlet, i.e. in our case we UTF-8-decode the servlet path 
as well as the query string. From your comment I read that you consider 
querystring parameters the same as servlet paths but the default behaviour in 
Tomcat is not the same.
As I wrote we have passed UTF-8-Strings via querystring parameters for a long 
time. getParameter() does the URLdecoding and afterwards we manually UTF-8-
decode this string.
Now we have started to use the servlet path and use getPathInfo() and expected 
the same and run into the problem described here.
With your connector attributes I think we should Tomcat let UTF-8-decode the 
URL but then we have to omit the UTF-8-decoding from our servlet. But is that 
portable across other servlet containers? We will not use your suggestion but 
use our own implementation of getPathInfo().

Again in short: IMO the servlet path obtained by getPathInfo() should be 
handled the same way as the querystring handled by getParameter().

Michael

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