I updated the ServletController code not to depend on HttpServletRequest.getPathInfo() for determining the base URI, so even if the underlying servlet controller does not deal properly with some specific symbols such as encoded '/'s, etc, it won't be now exposed via getPathInfo, so 6.0.10 should also be OK with the latest snapshots
Sergey On Thu, Mar 10, 2011 at 10:37 PM, Sergey Beryozkin <[email protected]>wrote: > Hi > > > On Thu, Mar 10, 2011 at 10:19 PM, Keith Hawes <[email protected]> wrote: > >> I tried again just now, and am still seeing tomcat eat the second /, If I >> double encode then I'm OK but i then have to decode again on the other >> side. >> >> If it helps I've also tried with out encoding and get the same results >> // becoming / >> >> Did you have @Encode in your test, my test case does not have it. >> >> Thank you for your efforts, I'll investigate further on our end. My >> service is using tomcat 6.0.10 >> >> I only use @Encoded to confirm that the encoded value reached the method > without any issues, it does not have any effect on this issue... > Can you please try 6.0.29 - this is the version I use... > > thanks, Sergey >
