Hmm.. we noticed another issue. When the Loadbalancer has SSL but internally redirects the requst to a tomcat not on SSL (to avoid having SLL at every level in the internal restricted network) the Seam framework sends back 302 (page moved) for every request to the login-view-id page and we get an infinite loop of 302 location login-view-id.
If the tomcat has SSL setup, it works as expected. Does the Seam framework explicitly check if the current host scheme is SSL even if the request URL is https? Thanks, Nik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118755#4118755 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118755 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
