0 Replies Latest reply on Mar 26, 2009 4:42 AM by chetanpadhye

    session cookies are different for https and http -


      Problem is that when I configure the page for ssl there is port switch for pages and in that case identity is created log message appears twice on console. When this happens all the components get set to null.

      What I think is when client request comes it is new session and seam creates identity object. This is just identity object in this request session. We can navigate to pages which are configured as login required false. The beans for these pages are kept in session scope so those beans are also part of this request session. But when port change occurs it is creating new request session the same way it will create for new request. This results in creation of components but as those are new components for this new request which is because of port change does not have any values which we are expecting.

      I think this might be because session cookies are different for https and http

      What is the way i can handle this ?