2smart4u wrote:
>
> More or less, it drops the context from the Cookie-path, meaning the
> cookie is valid for all contexts.
>
Hi Gregor,
Does this mean that session/servletContext is shared between contexts? E.g.
if I have some attribute in session/application contexts in webapp1 would it
be accesible in webapp2?
So my understanding how it works:
1) There is no cookie in browser - it will loadbalance to any engine
2) There is cookie in browser - it will loadbalance to engine which already
has session - since cookie has no context path
Thank you,
Andrey.
--
View this message in context:
http://old.nabble.com/Always-load-balance-to-same-box-with-different-tomcat-contexts-tp27946266p27950926.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
