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=23929>. 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=23929 request.setCharacterEncoding(String) doesn't work [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-10-20 10:37 ------- Sorry, there's no bug. BZ is not there to discuss design decisions. If you want to do so, post on tomcat-dev. The only standard for URL encoding is to use UTF-8, but nobody follows the standard. You can also now configure the URI encoding in the connector. If you insist on using i18n with URL parameters, the result is that it won't work reliably, but of course, you're free to do what you want ;-) Please do not reopen the report. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
