Jean-Frederic wrote:
What about url like /context-a/../context-b/? There could be a problem if the goal is not to map /context-b. Should we normalise /context-a/../context-b/ to /context-b and then do the mapping.
If the *original* URI is "/context-a/../context-b/" then apache httpd normalizes this (correctly) to "/context-b/". If JkMount matches /conext-a" we don't forward, if it matches "/context-b" we forward. I don't get the point here. What kind of problem (encoding, decoding, mod_jk, Tomcat) do you want to produce with sch a URI?
By the way: for such a simple URI httpd and Tomcat both do the same normalization (resulting in "/context-b").
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
