-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Mike,
On 2/14/13 9:51 AM, Mike Wilson wrote: > I can see that even if you specify URIEncoding=UTF-8 in > server.xml, calls to HttpServletRequest.getRequestURI() will still > return an undecoded String. (This is probably because of the > "specification text" in javadoc: "The web container does not decode > this String.") > > My question is if this behaviour has changed throughout Tomcat > versions? > > We got problems with this when upgrading to Tomcat 7, and it seems > we have been getting decoded strings previously when we were using > Jboss 4 (based an Tomcat 5.5 IIRC). I think you may be confusing character encoding versus URL encoding. The <Connector>'s URIEncoding is a character encoding (e.g. ISO-8859-1, UTF-8, etc.) that will be used to convert bytes into characters while URL encoding is the transformation of characters like "+" into spaces, %-decoding, etc. What kind of encoding is (or isn't) happening that seems surprising? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlEdQ6AACgkQ9CaO5/Lv0PCaDwCgkM6PsHbdLNEcHa+Tl6ZsNrWk D/sAoMCTm5yBd/Uzm19K/zxJ5oS/6CWr =eqtR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
