Re: Mutual SSL client certificate validation(Key Usage and Extended Key Usage) in tomcat server

On 05/02/2018 02:14, Indunil Rathnayake wrote: Hi, On 2 February 2018 at 19:55, Christopher Schultz < ch...@christopherschultz.net> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/2/18 5:35 AM, Mark Thomas wrote: On 02/02/18 04:06, Christopher Schultz wrote: It seems

Re: jsessionid path parameter: Is this compliant with the Servlet 3.0 spec?

Thanks, that is pretty clear and unambiguous, as is "The name of the parameter must be jsessionid." When the spec is in conflict with itself, I'm happy to consider Tomcat the reference implementation. The reason a session cookie name had to be specified in the first place was because we

Re: Mutual SSL client certificate validation(Key Usage and Extended Key Usage) in tomcat server

Hi, On 2 February 2018 at 19:55, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On 2/2/18 5:35 AM, Mark Thomas wrote: > > On 02/02/18 04:06, Christopher Schultz wrote: > > > > > > > >> It seems reasonable for Tomcat

Re: jsessionid path parameter: Is this compliant with the Servlet 3.0 spec?

On 03/02/18 21:55, Dave Glasser wrote: > This text is based on a stackoverflow question I posted earlier today: > https://stackoverflow.com/questions/48600576/jsessionid-as-path-parameter-not-working-in-tomcat/48602272 > > > I'm using Tomcat 7.0.84, and my web app uses the Servlet 3.0 deployment