I think the simplest way would just to be recompile Tomcat and
hardcode the domain to your own purpose.
The LB was the easiest for me but I'm running into different issues
now...
greg
On Feb 27, 2008, at 5:56 PM, Raul Acevedo wrote:
You ended up having your load balancer modify the cooki
You ended up having your load balancer modify the cookies so it could
alter the domain? Yikes.
Is there any way to do this in Tomcat? From other posts I've seen:
http://marc.info/?l=tomcat-user&m=120179086031396&w=2
http://www.esus.be/blog/?p=3
It looks like it's possible to use a valve, but t
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,
ht
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
