[JBPAPP-7183] Back port fix - Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE - JBoss Issue Tracker

XML

Word

Printable

Affects:

Release Notes
Release Notes Text:

Hide
When using the <s:token /> tag in JSF, the <systemitem>javax.faces.ClientToken</systemitem> cookie that is created sometimes had an empty ("") path. The cookie was then not accepted in certain versions of <application>Windows Internet Explorer</application> and the following error message was returned:

<screen>
viewId: /myPage.xhtml - No client identifier provided.
</screen>

This update ensures that when an empty path is detected, "/" is set as the cookie value. As a result, the cookie is accepted by all browsers and the above mentioned error message is no longer returned.

Show
When using the <s:token /> tag in JSF, the <systemitem>javax.faces.ClientToken</systemitem> cookie that is created sometimes had an empty ("") path. The cookie was then not accepted in certain versions of <application>Windows Internet Explorer</application> and the following error message was returned: <screen> viewId: /myPage.xhtml - No client identifier provided. </screen> This update ensures that when an empty path is detected, "/" is set as the cookie value. As a result, the cookie is accepted by all browsers and the above mentioned error message is no longer returned.
Release Notes Docs Status:
Documented as Resolved Issue
Docs QE Status:
NEW

Please port ~~JBSEAM-4701~~ into the Seam version shipped with EAP 5.1.2.

is duplicated by

JBPAPP-7269 <s:token> - cookie identifying the browser (javax.faces.ClientToken) might contain illegal characters

is related to

JBSEAM-4701 Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE