https://issues.apache.org/bugzilla/show_bug.cgi?id=45406
--- Comment #9 from Ran Rubinstein <[EMAIL PROTECTED]> 2008-07-17 01:17:48 PST --- (In reply to comment #8) > Of course, whether or not that is a good idea is another question. > > So yes, if a server needs to support these kinds of URIs, it needs to > workaround the limitations of the servlet engine (another way would be to use > getRequestURI(), and parse that directly). > Using getRequestURI() and parsing myself is the simple part. Since the parameter map in the HttpServletRequest is immutable, I need to use my own subclass for the request and use it throughout my application (and it can't be forwarded to external web applications). That solution is not very elegant. I'm not in a place to judge whether encoding URL's with non-ascii-superset encodings is legal or not, but: If non-ascii-superset-encoded URIs are legal, I think tomcat should support them. Tomcat has the APIs to setCharacterEncoding() and useBodyEncodingForURI's, which don't limit the encoding to an ascii superset. It's looks like a simple matter of changing how URI's are decoded, to be compliant with the %-encoding rules. If these URI's are illegal, perhaps tomcat should throw some kind of exception when when setCharacterEncoding is called with an 'illegal' encoding, and useBodyEncodingForURI is true. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
