Tomcat version: 8.0.43
java: 1.8.0_05
Hello,
On some web browsers, clients are able to enter uri's with unescaped
illegal characters (eg: "|" or pipe).
This causes an IllegalArgumentException to be thrown and a 400 response
code.
This behavior is reported here:
https://bz.apache.org/bugzilla/show
Benoit Maisonny wrote:
Sorry, not always easy to keep a thread with the huge traffic on this list.
Christopher Schultz wrote:
Benoit,
Benoit Maisonny wrote:
| Christopher Schultz wrote:
|>
|> Benoit,
|>
|> Benoit Maisonny wrote:
|> | I suspect someone forgot to encode the URI in the Location:
Sorry, not always easy to keep a thread with the huge traffic on this list.
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benoit,
Benoit Maisonny wrote:
| Christopher Schultz wrote:
|>
|> Benoit,
|>
|> Benoit Maisonny wrote:
|> | I suspect someone forgot to encode th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benoit,
Benoit Maisonny wrote:
| Christopher Schultz wrote:
|>
|> Benoit,
|>
|> Benoit Maisonny wrote:
|> | I suspect someone forgot to encode the URI in the Location: HTTP header
|> | on the 302 response, but maybe there is something missing in our
Christopher Schultz wrote:
Benoit,
Benoit Maisonny wrote:
| I suspect someone forgot to encode the URI in the Location: HTTP header
| on the 302 response, but maybe there is something missing in our
| configuration?
What is the default character set of the running JVM?
UTF-8, according to ja
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benoit,
Benoit Maisonny wrote:
| I suspect someone forgot to encode the URI in the Location: HTTP header
| on the 302 response, but maybe there is something missing in our
| configuration?
What is the default character set of the running JVM?
- -ch
Hi,
I see weird URI encoding behaviour from DefaultServlet when a redirect
occurs.
Context: Tomcat 5.5.25, with the Connector configured with
URIEncoding="UTF-8". User wants to list the contents of a directory
served by DefaultServlet. The directory's name contains a non-ASCII
character (e with
