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

2017-04-24 Thread Mark Thomas
On 24/04/17 15:57, Tobias Brennecke wrote: > On 24/04/17 14:24, Mark Thomas wrote: > >> >>> 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. >> This is now complete for 9.0.x, 8.5.x, 8.0.x and

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

2017-04-24 Thread Tobias Brennecke
On 24/04/17 14:24, Mark Thomas wrote: > >> 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. > This is now complete for 9.0.x, 8.5.x, 8.0.x and 7.0.x. > >> I am concerned that fixing this may break

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

2017-04-24 Thread Naga Ramesh
omas [mailto:ma...@apache.org] Sent: Monday, April 24, 2017 5:54 PM To: Tomcat Users List Subject: Re: + character is always encoded in url path after request dispatch since #59317 On 21/04/17 20:54, Mark Thomas wrote: > On 21/04/17 17:27, Tobias Brennecke wrote: > > > >>

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

2017-04-24 Thread Mark Thomas
On 21/04/17 20:54, Mark Thomas wrote: > 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

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

2017-04-21 Thread Mark Thomas
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