Jarecsni János wrote:
Hi,
it seems that tomcat uses the /contextname path when creating the cookie
for the JSESSIONID. Since we use Apache in front of Tomcat and we use
mod_rewrite with mod_proxy to provide aliasing of dynamic Java resources, it
is not working for us.
You should explain
the path in the session cookie (Tomcat 402b)
|
|
|Jarecsni János wrote:
|
| Hi,
|
| it seems that tomcat uses the /contextname path when creating
|the cookie
| for the JSESSIONID. Since we use Apache in front of Tomcat and we use
| mod_rewrite with mod_proxy to provide aliasing of dynamic Java
-frederic clere
|Sent: Friday, February 15, 2002 12:16 PM
|To: Tomcat Developers List
|Subject: Re: setting the path in the session cookie (Tomcat 402b)
|
|
|Jarecsni János wrote:
|
| Hi,
|
| it seems that tomcat uses the /contextname path when creating
|the cookie
| for the JSESSIONID. Since
Hi Jean-Frederic,
I definitely use it! :) I use mod_jk. I have the appropriate JkMount
settings included in httpd.conf. Everything works fine. It is the _aliasing_
that cannot be done.
so I can do
http://apache.virtual.host/jbossapplicationcontext/something?someparameter
what I cannot do is:
