[
https://issues.apache.org/jira/browse/DELTASPIKE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131450#comment-15131450
]
Sean Flanigan commented on DELTASPIKE-1071:
-------------------------------------------
Yes on both questions.
I can reproduce the problem with JSF playground (1.5.2) on the page
{{http://localhost:8080/ds/views/windowhandling/lazy/test.xhtml}} when I edit
the URLs as previously described (running on WildFly).
As far as I can tell from the specs, {{?&dswid=XYZ}} should be interpreted the
same way as {{?dswid=XYZ}} because {{&}} is just a delimiter. The web servers I
tried seem to treat them the same way, with or without the extra {{&}}.
Even if the intention is not to support the syntax {{?&dswid=XYZ}}, the fact
that it leads to window cloning has got to be a bug IMO.
> URLs like ?&dswid=XYZ leads to window cloning
> ---------------------------------------------
>
> Key: DELTASPIKE-1071
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1071
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 1.5.1
> Reporter: Sean Flanigan
> Assignee: Thomas Andraschko
>
> Using default window mode on Chrome (equates to LAZY?), if a clickable URL
> ends in {{?&dswid=XYZ}}, opening that link in a new tab clones the old tab's
> {{window.name}} and {{dswid}}, instead of generating a new id.
> I had this (very confusing) problem in my application when a urlrewrite
> outbound-rule accidentally used {{&dswid=XYZ}} instead of {{?dswid=XYZ}}, but
> for simple applications it is easiest to reproduce like this:
> 1. visit a page URL which ends with {{?dswid=XYZ}}
> 2. use the javascript console to check {{window.name}}
> 3. edit the URL so that it ends with {{?&dswid=XYZ}}
> 4. paste the edited URL into a fresh browser tab (where {{window.name}} is
> empty)
> 5. use the javascript console to check {{window.name}} for the new tab
> Both tabs have the same {{window.name}}, which leads to all window-based
> scopes in the session being shared for future requests in the affected tabs.
> I haven't dug into the code too closely, but I suspect {{windowhandler.js}}
> is setting {{window.name}} when it sees {{&dswid}} in the URL, instead of
> triggering a lazy redirect as I think it should.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
