https://issues.apache.org/bugzilla/show_bug.cgi?id=50065
--- Comment #1 from Chuck Caldarale <chuck.caldar...@unisys.com> 2010-10-09 22:38:38 EDT --- (In reply to comment #0) > It seems that after URL-decoding a parameter value that value is treated as a > string in some 1-byte charset, but not as a string encoded with a charset > specified by http's request character encoding. So where in the RFCs or EE specs can you find justification for the behavior you wish to see versus the behavior Tomcat exhibits? To quote from section 14.17 of RFC 2616: "The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient" Note the reference to the entity-body; it says nothing about the parameters on the URI - which are interpreted as ISO-8859-1, since there is no standard to allow URIs in other character sets. You can specify the <Connector> attributes URIEncoding or useBodyEncodingForURI in the Tomcat config if you want to change the default behavior. -- 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: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
