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 2001/10/25 15:31:49 UTC
DO NOT REPLY [Bug 4416] New: -
URI En/Decoding not working
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=4416>.
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=4416
URI En/Decoding not working
Summary: URI En/Decoding not working
Product: Tomcat 3
Version: 3.3 Final
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Major
Priority: Other
Component: Encoding
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: stefan.eissing@greenbytes.de
DecodeInterceptor takes huge effort to guess the encoding, however
when decoding the request URI internal, it disregards the encoding
and uses 8859-1.
When the servlet the calls request.getRequestURI(), the request
internally encodes the decoded URI again (which is correct) and
uses the correct charset. This obviously does not roundtrip when
UTF-8 chars are encoded in the URI.
When setting the server.xml attribute saveOriginal="true", the unparsed
URI is saved in core/Request and returned on getRequestURI(). This works
as (undocumented) workaround for us.