Hi Remy,
Okay, re-reviewed the original 22666 thread. To complete this thread, I'll assume the following from RFC2718 is our justification for the new behavior:
Unless there is some compelling reason for a particular scheme to do otherwise, translating character sequences into UTF-8 (RFC 2279) [3] and then subsequently using the %HH encoding for unsafe octets is recommended.
Tomcat will default to US-ASCII instead of UTF-8 so it won't break too many existing webapps. If there are other parts to this story, I would be interested in learning of them.
I'm still concerned that this makes Tomcat less useful by creating deployment problems for webapps that aren't technically broken. However, these issues were covered in the prior e-mail thread (http://www.mail-archive.com/[EMAIL PROTECTED]/msg46479.html), so I'll drop the issue. Thanks.
The idea for the change is that there's no compelling reason (except hacking) to have one part of the URI be in some encoding (US-ASCII or UTF-8, if you want to have any chance of mapping it successfully), and the rest encoded in something else.
There's indeed a bug thread on this issue, and I was on your side at first.
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
