Same issue here. I had to go through some headache with the load
balancer to duplicate JSESSIONID cookies so they'd be on the domain
level and not just at the host level.
greg
On Feb 27, 2008, at 5:36 PM, Raul Acevedo wrote:
Our app server will be accessed through two different domains,
http://www.foo.com and https://secure.foo.com. This won't work if the
JSESSIONID cookie domain continues to default to www.foo.com.
How can I configure JSESSIONID so the domain is .foo.com?
Raul Acevedo
http://www.cantara.com
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
