Re: latest situation with escaped path delimiters in URI

2019-02-05 Thread Garret Wilson
On 2/5/2019 1:15 PM, Mark Thomas wrote: … Migratation to git has been in planning for a while. We are pretty much ready to pull the trigger. It is largely waiting for someone to have the time to do it when there aren't other more urgent things to be dealt with. I'd expect it to happen in the

Re: latest situation with escaped path delimiters in URI

2019-02-05 Thread Mark Thomas
On 05/02/2019 14:51, Garret Wilson wrote: > On 2/3/2019 9:34 PM, Mark Thomas wrote: >> >>>   * If this setting is still needed in some cases, is there any way to >>>     control it without resorting to a system property? (System >>>     properties are not very flexible, and Tomcat has many layers

Re: latest situation with escaped path delimiters in URI

2019-02-05 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Garret, On 2/4/19 17:22, Garret Wilson wrote: > On 2/4/2019 7:31 PM, Christopher Schultz wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> Garret, >> >> On 2/3/19 16:20, Garret Wilson wrote: >>> If we want to look up the thing

Re: latest situation with escaped path delimiters in URI

2019-02-05 Thread Garret Wilson
On 2/3/2019 9:34 PM, Mark Thomas wrote:  * If this setting is still needed in some cases, is there any way to    control it without resorting to a system property? (System    properties are not very flexible, and Tomcat has many layers of more    manipulable settings, as you all would know

Re: latest situation with escaped path delimiters in URI

2019-02-04 Thread Garret Wilson
On 2/4/2019 7:31 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Garret, On 2/3/19 16:20, Garret Wilson wrote: If we want to look up the thing identified by https://example.info/foobar, we would need to issue a request to

Re: latest situation with escaped path delimiters in URI

2019-02-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Garret, On 2/3/19 16:20, Garret Wilson wrote: > If we want to look up the thing identified by > https://example.info/foobar, we would need to issue a request to > https://example.com/https%3A%2F%2Fexample.info%2Ffoobar/description Why > are you

Re: latest situation with escaped path delimiters in URI

2019-02-04 Thread Rainer Jung
Am 03.02.2019 um 22:20 schrieb Garret Wilson: Hi, all. I've stumbled on a situation I need some clarity on. As is typical, there's all sorts of information floating around, most of it more than a decade old, with no indication of what the current status is. Our team is creating a RESTful API

Re: latest situation with escaped path delimiters in URI

2019-02-04 Thread Mark Thomas
On 03/02/2019 23:58, Garret Wilson wrote: > On 2/3/2019 3:34 PM, Mark Thomas wrote: >> ... >> There is an open question what Tomcat should do with %2F sequences. > > "What Tomcat should do" in what context? The servlet and JAX-RS specs > may be clear about whether decoded or "raw" APIs should be

Re: latest situation with escaped path delimiters in URI

2019-02-03 Thread Garret Wilson
On 2/3/2019 3:34 PM, Mark Thomas wrote: ... There is an open question what Tomcat should do with %2F sequences. "What Tomcat should do" in what context? The servlet and JAX-RS specs may be clear about whether decoded or "raw" APIs should be returned from the various API methods. But I guess

Re: latest situation with escaped path delimiters in URI

2019-02-03 Thread Mark Thomas
On 03/02/2019 21:20, Garret Wilson wrote: > Hi, all. I've stumbled on a situation I need some clarity on. As is > typical, there's all sorts of information floating around, most of it > more than a decade old, with no indication of what the current status is. > > Our team is creating a RESTful