On 05/02/2018 03:18, Dave Glasser wrote:
> 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.
Technically, the RI is glassfish.
This sort
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 initiall
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
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
descriptor. The web.xml file contains this:
