[
https://issues.apache.org/jira/browse/MTOMCAT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401876#comment-15401876
]
Martin Grotzke edited comment on MTOMCAT-234 at 8/1/16 11:2
[
https://issues.apache.org/jira/browse/MTOMCAT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401876#comment-15401876
]
Martin Grotzke commented on MTOMCAT-234:
Also waiting for this. While
[
https://issues.apache.org/jira/browse/MTOMCAT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852750#comment-13852750
]
Martin Grotzke commented on MTOMCAT-250:
Just for the record, there'
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.
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
Hi,
in r1164481 the notification of ServletRequestListeners was moved from
StandardContextValve to StandardHostValve.
This causes issues for memcached-session-manager (msm) in combination
with openwebbeans (OWB).
In short, msm is an alternative session manager that uses memcached as
for session
