Re: + character is always encoded in url path after request dispatch since #59317

On 21/04/17 17:27, Tobias Brennecke wrote: > My question is whether this behavior is intended or if this is a bug. That looks like a bug to me. We need to go through and check all the places URLs are being encoding and check it is being done correctly. I am concerned that fixing this may brea

Re: Extended Validation Certificates Support JNDIRealm

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Lucas, (Bringing this back onto the list; apologies for inadvertently replying off-list) On 4/21/17 12:25 PM, Lucas S. Silva wrote: > Hi Christopher, > > Thanks for the reply. > > Yes, the goal is to check the user certificate against some > con

+ character is always encoded in url path after request dispatch since #59317

Dear list, in https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 HttpServletRequest.getRequestURI() has been changed for Tomcat 7.0.70 onwards to always return an encoded URI, which matches the servlet 3.0 specification. However the encoding for the path component of the url seems to be incorrec