-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 2/8/12 4:34 PM, Mark Thomas wrote:
> On 08/02/2012 21:25, Christopher Schultz wrote: Unfortunately, the
> servlet spec is far from clear on how path parameters should be
> handled. I hope to get clarity in 3.1 with [1]
In fact, it might actu
2012/2/9 Christopher Schultz :
>
> There was a change in 6.0.33 (and it has always been the case in
> 7.0.x?) that HttpServletRequest.getRequestURI now returns path
> parameters as part of the URI. That notably includes the URL-encoded
> jsessionid that Tomcat uses when the availability of cookies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terrence,
On 2/9/12 5:16 PM, Terence M. Bandoian wrote:
> On 1:59 PM, Christopher Schultz wrote:
>> Is it safe to simply remove everything after the initial ";" if
>> I'm not interested in any path parameters? I don't want to just
>> trim-off that kin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 2/8/12 4:34 PM, Mark Thomas wrote:
> On 08/02/2012 21:25, Christopher Schultz wrote:
>> Mark,
>
>> On 2/8/12 3:37 PM, Mark Thomas wrote:
>>> On 08/02/2012 20:35, Christopher Schultz wrote:
Can anyone think of a reason I can't just [chop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2012 21:25, Christopher Schultz wrote:
> Mark,
>
> On 2/8/12 3:37 PM, Mark Thomas wrote:
>> On 08/02/2012 20:35, Christopher Schultz wrote:
>>> Can anyone think of a reason I can't just [chop-off everything
>>> after the first ";"]?
>
>> Ye
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 2/8/12 3:37 PM, Mark Thomas wrote:
> On 08/02/2012 20:35, Christopher Schultz wrote:
>> Can anyone think of a reason I can't just [chop-off everything
>> after the first ";"]?
>
> Yes. Path parameters can occur at any part of the path.
So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/2012 20:35, Christopher Schultz wrote:
> All,
>
> There was a change in 6.0.33 (and it has always been the case in
> 7.0.x?) that HttpServletRequest.getRequestURI now returns path
> parameters as part of the URI. That notably includes the
>
