You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/06/30 07:47:10 UTC

[jira] [Commented] (IGNITE-3161) WebSession: Session must be created on demand, not always.

    [ https://issues.apache.org/jira/browse/IGNITE-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356686#comment-15356686 ] 

Vladimir Ozerov commented on IGNITE-3161:
-----------------------------------------

This ticket also fixes IGNITE-3160:
"When user change session ID, we call invalidate() method on our session after leaving the filter.
This call will invalidate genuine session as well, which is wrong. Looks like our session ID change is broken."

> WebSession: Session must be created on demand, not always.
> ----------------------------------------------------------
>
>                 Key: IGNITE-3161
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3161
>             Project: Ignite
>          Issue Type: Bug
>          Components: websession
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 1.7
>
>
> Our filter will always creates new session (both in Ignite and in container). This is wrong, as session must be created only when it is really requested through {{HttpRequest.getSession(true)}} call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)