[ https://issues.jboss.org/browse/JBSEAM-4906?page=com.atlassian.jira.plugi... ] Tayfun Gokmen Halac edited comment on JBSEAM-4906 at 3/9/12 1:32 PM: --------------------------------------------------------------------- That's not the same issue. JBSEAM-4701 considers empty cookie path. The problem is about constructed authentication token in autoLogin mode of RememberMe. After Remember-Me generates an authentication token, it is encoded using Base64. But, Base64 encoding contains equals ("=") signs at the end. For this reason, Tomcat converts the cookie into version 1 form since it has a character incompatible with version 0. Internet Explorer cannot understand max-age property in cookie of version 1. See isToken2() and maybeQuote2() methods in org.apache.tomcat.util.http.ServerCookie.java. I am producing the issue on JBoss-6.0.0.Final with Seam 2.2.2. was (Author: tayfunhalac): That's not the same issue. JBSEAM-4701 considers empty cookie path. The problem is that about constructed authentication token. After Remember-Me generates an authentication token, it is encoded using Base64. But, Base64 encoding contains equals ("=") signs at the end. For this reason, Tomcat converts the cookie into version 1 form since it has a character incompatible with version 0. Internet Explorer cannot understand max-age property in cookie of version 1. See isToken2() and maybeQuote2() methods in org.apache.tomcat.util.http.ServerCookie.java. I am producing the issue on JBoss-6.0.0.Final with Seam 2.2.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4906?page=com.atlassian.jira.plugi... ] Tayfun Gokmen Halac edited comment on JBSEAM-4906 at 3/9/12 1:36 PM: --------------------------------------------------------------------- That's not the same issue. JBSEAM-4701 considers empty cookie path. The problem is about constructed authentication token in autoLogin mode of RememberMe. After Remember-Me generates an authentication token, it is encoded using Base64. But, Base64 encoding contains equals ("=") signs at the end. For this reason, Tomcat converts the cookie into version 1 form since it has a character incompatible with version 0. Internet Explorer cannot understand max-age property in cookie of version 1. See isToken2() and maybeQuote2() methods in org.apache.tomcat.util.http.ServerCookie.java. I am producing the issue on JBoss-6.0.0.Final with Seam 2.2.2. This issue looks like JBSEAM-4398. was (Author: tayfunhalac): That's not the same issue. JBSEAM-4701 considers empty cookie path. The problem is about constructed authentication token in autoLogin mode of RememberMe. After Remember-Me generates an authentication token, it is encoded using Base64. But, Base64 encoding contains equals ("=") signs at the end. For this reason, Tomcat converts the cookie into version 1 form since it has a character incompatible with version 0. Internet Explorer cannot understand max-age property in cookie of version 1. See isToken2() and maybeQuote2() methods in org.apache.tomcat.util.http.ServerCookie.java. I am producing the issue on JBoss-6.0.0.Final with Seam 2.2.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira