[jboss-jira] [JBoss JIRA] (WFLY-2884) WildFly issuing new cookie for every request, when faces view is not directly in root (/ )

[André Prata (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944426#comment-12944426 ] 

André Prata commented on WFLY-2884:
-----------------------------------

Appears to be solved in 8.0.0.Final! :)
                
> WildFly issuing new cookie for every request, when faces view is not directly in root (/ )
> ------------------------------------------------------------------------------------------
>
>                 Key: WFLY-2884
>                 URL: https://issues.jboss.org/browse/WFLY-2884
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.CR1
>            Reporter: André Prata
>            Assignee: Stuart Douglas
>         Attachments: test.war
>
>
> Hello everyone.
> I have seen possibly similar issues, but people just aren't able to reproduce them anymore and they seem to be closed without further inspection. Maybe this is the same problem.
> I started seeing a problem in a new application I'm developing. For views such as "/view.xhtml" everything is working fine. But if I move the view to another directory, e.g. "/admin/view.xtml", I get ViewExpiredExceptions when interacting with backing beans.
> Two things:
> - This does not happen if there is already a cookie associated with the session. I.e., I can only reproduce the issue if the first cookie is created by accessing "/admin/view.xhtml". Accessing something in the root and then the other directories works just fine (the server won't send set-cookies again).
> - When accessing "/admin/view.xhtml" new cookies are issued for every .xhtml request. Fetching PrimeFaces .js.xhtml files after the initial page is loaded, for example, triggers new sessions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira