Mike Wilson wrote:
Mark Thomas wrote:
On 17/02/2013 16:54, André Warnier wrote:
Mike Wilson wrote:
Example 2: path /ä in "binary" Unicode
GET /.. [0xC3,0xA4]
request.getRequestURI() -> "/.." [0xC3,0xA4]
request.getPathInfo() -> "/ä"
I believe that your example #2 above is simply
Mark Thomas wrote:
> On 17/02/2013 16:54, André Warnier wrote:
> > Mike Wilson wrote:
>
>
>
> >> Example 2: path /ä in "binary" Unicode
> >> GET /.. [0xC3,0xA4]
> >> request.getRequestURI() -> "/.." [0xC3,0xA4]
> >> request.getPathInfo() -> "/ä"
>
>
>
> > I believe that your example #
Mike Wilson wrote:
...
Example 2: path /ä in "binary" Unicode
GET /.. [0xC3,0xA4]
To nitpick : this is not "binary Unicode". It is simply non-URL-encoded, raw UTF-8, which
is itself an encoding of Unicode.
The Unicode "codepoint" of "ä" is 0xE4 (decimal 228), usually represented as
U+00
On 17/02/2013 16:54, André Warnier wrote:
Mike Wilson wrote:
Example 2: path /ä in "binary" Unicode
GET /.. [0xC3,0xA4]
request.getRequestURI() -> "/.." [0xC3,0xA4]
request.getPathInfo() -> "/ä"
I believe that your example #2 above is simply illegal.
One is not supposed to send
Mike Wilson wrote:
Hi Chris,
I'm aware of the two levels of encoding but I'm wondering whether
servlet specification writers were :-)
Here are two examples from Tomcat 7 running with URIEncoding="UTF-8".
Example 1: path /ä in URL-encoded Unicode as sent from browser
GET /%C3%A4
request.ge
On 14.02.2013 14:17, Philippe Bossu wrote:
> We have a mod_jk in version 1.2.28 with Apache 2.16 fronting a Tomcat
> server in version 6 on JDK6.
>
> We are facing long response times and timeouts from time to time.
> Mod_jk log files show the following errors:
>
> [][X] [error]
Hi Chris,
I'm aware of the two levels of encoding but I'm wondering whether
servlet specification writers were :-)
Here are two examples from Tomcat 7 running with URIEncoding="UTF-8".
Example 1: path /ä in URL-encoded Unicode as sent from browser
GET /%C3%A4
request.getRequestURI() -> "/%C3
