[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4701:
----------------------------------
Fix Version/s: 2.3.1.CR1
Cookie path being set to empty string via getRequestContextPath
forming invalid cookies in IE
---------------------------------------------------------------------------------------------
Key: JBSEAM-4701
URL:
https://issues.jboss.org/browse/JBSEAM-4701
Project: Seam 2
Issue Type: Bug
Affects Versions: 2.1.2.GA, 2.3.0.CR1
Reporter: Brian Dill
Assignee: Marek Novotny
Fix For: 2.3.1.CR1
Attachments: ClientUidSelector.patch
When using <s:token /> in JSF the javax.faces.ClientToken cookie that is created
can potentially have an empty ("") path which will cause it to not be accepted
in some versions of Internet Explorer. The following code in ClientUidSelector is the
problem.
setCookiePath(FacesContext.getCurrentInstance().getExternalContext().getRequestContextPath());
This bug can be manifested as "viewId: /myPage.xhtml - No client identifier
provided." I'll try to post a patch file here asap.
--
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