[JBoss JIRA] Created: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
3:46 p.m.
Cookie path being set to empty string via getRequestContextPath forming invalid cookies in
IE
---------------------------------------------------------------------------------------------
Key: JBSEAM-4701
URL: https://jira.jboss.org/browse/JBSEAM-4701
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.2.GA
Reporter: Brian Dill
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://jira.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugin....
]
Brian Dill updated JBSEAM-4701:
-------------------------------
Attachment: ClientUidSelector.patch
Here's a potential SVN patch.
Cookie path being set to empty string via getRequestContextPath
forming invalid cookies in IE
---------------------------------------------------------------------------------------------
Key: JBSEAM-4701
URL: https://jira.jboss.org/browse/JBSEAM-4701
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.2.GA
Reporter: Brian Dill
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Sean Flanigan commented on JBSEAM-4701:
---------------------------------------
This also affects Firefox 4.0 when I use the root context for my webapp (Seam 2.2.0.GA).
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
Reporter: Brian Dill
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Sean Flanigan commented on JBSEAM-4701:
---------------------------------------
See also https://issues.jboss.org/browse/SEAMSECURITY-9
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
Reporter: Brian Dill
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:47 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration updated JBSEAM-4701:
--------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=691963
Forum Reference: http://seamframework.org/Community/SeamTokenTagProblemCSRF (was:
http://seamframework.org/Community/SeamTokenTagProblemCSRF)
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
Reporter: Brian Dill
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4701:
----------------------------------
Assignee: Marek Novotny
Fix Version/s: 2.3.0.ALPHA
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=691963 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=691963)
Forum Reference: http://seamframework.org/Community/SeamTokenTagProblemCSRF (was:
http://seamframework.org/Community/SeamTokenTagProblemCSRF)
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
Reporter: Brian Dill
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:45 a.m.
New subject: [JBoss JIRA] Resolved: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Novotny resolved JBSEAM-4701.
-----------------------------------
Resolution: Done
replaced random string token with random alphabeta string with only letters and numbers
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
Reporter: Brian Dill
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Jason Shepherd commented on JBSEAM-4701:
----------------------------------------
Also effects Seam 2.2.2.EAP5
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
Reporter: Brian Dill
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:16 a.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Schmidt reopened JBSEAM-4701:
-----------------------------------
I can reproduce the problem on Seam2.3.0.CR1 with IE9 on Windows 2k8 and JBoss AS
7.1.1.Final
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
Reporter: Brian Dill
Assignee: Marek Novotny
Fix For: 2.3.0.ALPHA
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
2:18 a.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Schmidt updated JBSEAM-4701:
----------------------------------
Fix Version/s: (was: 2.3.0.ALPHA)
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
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
2:18 a.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Schmidt updated JBSEAM-4701:
----------------------------------
Affects Version/s: 2.3.0.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
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
12:12 p.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration updated JBSEAM-4701:
--------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=691963 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=691963)
Forum Reference: http://seamframework.org/Community/SeamTokenTagProblemCSRF (was:
http://seamframework.org/Community/SeamTokenTagProblemCSRF)
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
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
12:12 p.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration updated JBSEAM-4701:
--------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=691963 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=691963)
Forum Reference: http://seamframework.org/Community/SeamTokenTagProblemCSRF (was:
http://seamframework.org/Community/SeamTokenTagProblemCSRF)
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
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
3:57 p.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
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
7:56 a.m.
New subject: [JBoss JIRA] (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE
[
https://issues.jboss.org/browse/JBSEAM-4701?page=com.atlassian.jira.plugi...
]
Marek Novotny resolved JBSEAM-4701.
-----------------------------------
Resolution: Done
added forgotten lines from patch
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
4247
days inactive
5015
days old
14 comments
6 participants
participants (6)
-
Brian Dill (JIRA) -
Jason Shepherd (JIRA)
-
Marek Novotny (JIRA)
-
Marek Schmidt (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Sean Flanigan (JIRA)