https://issues.apache.org/bugzilla/show_bug.cgi?id=50504
--- Comment #6 from Mark Thomas <ma...@apache.org> --- The query string remains as bytes until it is required (if at all). Take a look at Http11InputBuffer.parseRequestLine() in trunk and when it is called. Hence why setting the character encoding on the request (assuming they do that before they read the query string) allows applications to choose the encoding they want to use for the query string on a per request basis. The URI is a different matter. It gets used for mapping so it has to be decoded before the mapping can take place so a per web application URI decoding makes no sense. -- 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
