Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7183

Back port fix - Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE

XMLWordPrintable

    • Release Notes
    • Hide
      When using the &lt;s:token &#47;&gt; 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, "&#47;" 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 &lt;s:token &#47;&gt; 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, "&#47;" 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.
    • Documented as Resolved Issue
    • NEW

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

              mnovotny@redhat.com Marek Novotny
              rhn-support-jshepher Jason Shepherd
              Petr Penicka Petr Penicka (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: