On 06/15/2012 07:49 AM, Rainer Jung wrote:
> On 14.06.2012 21:45, Martin Grotzke wrote:
>> Wouldn't it be more safe for users that are not aware of this fact to
>> always generate a new sessionId?
>
> Empty session path was originally meant to support a portal situation.
> Using it there would be
Hi Martin,
On 14.06.2012 21:45, Martin Grotzke wrote:
Hi,
I'm wondering why Manager.createSession(String) takes a sessionId that
gets set on the new session.
When a client invokes session.invalidate() and afterwards
request.getSession() he will get a new session with the same/previous
session
Hi,
I'm wondering why Manager.createSession(String) takes a sessionId that
gets set on the new session.
When a client invokes session.invalidate() and afterwards
request.getSession() he will get a new session with the same/previous
session id (yes, this is only done when the sessionId was submitt
