André Warnier wrote:
>[...]
>Now, I should add that using [ and ] in URL's is not really something I would
>recommend, if only for legibility reasons. It will always make people wonder
>if what they're seeing in the logfile is normal, or if it's some programming
>syntax which "escaped" there.
>
Jesse Klaasse wrote:
[...]
Good.
Now, I should add that using [ and ] in URL's is not really something I
would recommend, if only for legibility reasons. It will always make
people wonder if what they're seeing in the logfile is normal, or if
it's some programming syntax which "escaped" ther
Jesse Klaasse wrote:
[...]
Good.
Now, I should add that using [ and ] in URL's is not really something I
would recommend, if only for legibility reasons. It will always make
people wonder if what they're seeing in the logfile is normal, or if
it's some programming syntax which "escaped" ther
André Warnier wrote:
>It would appear (from the logs), that there is some double-encoding of the URI
>going on.
>[snip]
>But, if somewhere along the line, a piece of code was receiving the encoded
>URI "http://.../test%5Bbrackets%5D.jsp";, and decided to re-encode it again
>using the "% hex hex
Try taking out the square brackets from the jsp part and see if it works
without them (http://localhost/testbrackets.jsp).
Also, you shouldn't need the /webapp if Tomcat is configured correctly.
Make sure your directory structure is correct.
Walter
-Original Message-
From: Jesse Klaasse
Jesse Klaasse wrote:
[snip]
Now, we try the whole link through the JK connector:
http://localhost/webapp/test[brackets].jsp
This doesn't work, and results in a 404 error (appearing in both IIS and
Tomcat's log as test%5Bbrackets%5D.jsp, Tomcat with a 404, IIS with a
200).
Thanks for the exc
