Thanks guys for all the replies. I did get it to work - by adding
logic to manually create/update a JSESSIONID cookie with the Domain
set to the parent domain (e.g., company.com).This logic could be
placed into a tomcat valve, or in some other place along the request
control flow. Wanting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Delbecq wrote:
| Perhaps you can create a
| custom valve to do so (Alter response to change cookie domain, alter
| request to change the other way) :)
You only have to change the outgoing cookie domain; the browser does not
send the
It's technically possible that cookies get shared accros domains,
setting the cookie domaine to .mydomain.com. However, it will be of no
help to you, because each subdomain runs it's own set of webapps in
tomcat. The session can't be shared across webapps. If you need to
shared datas with your
Thanks for the reply.
So, you're saying that if I have a single deployed webapp, and I just
enter a few such domains (e.g., c1.mydomain.com, c2.mydomain.com, etc)
into DNS to point to this server, that tomcat will automatically
instantiate a separate webapp instance for each access subdomain?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve,
Steve Parker wrote:
| So, you're saying that if I have a single deployed webapp, and I just
| enter a few such domains (e.g., c1.mydomain.com, c2.mydomain.com, etc)
| into DNS to point to this server, that tomcat will automatically
|
