Unfortunately I think you might need to run multiple instances of Tomcat
in that case:( As you can't give multiple webapps a cookie with a "/"
path. If you find any other solutions, however, please let me know:)
Liam Morley
Rick Mills wrote:
>Hi
>
>Thanks for that, it was exactly what was hap
Hi
Thanks for that, it was exactly what was happening!
Moving the context for the bodypainting WAR file to root, and changing the
proxy pass to map http://www.bodypainting.co.uk/ to http://localhost:8000/
has fixed the problem, and my session tracking now works as expected.
I now need to work o
Rick,
I'm pretty sure that this is the same issue that I've experienced.
First, try mapping to "/bodypainting/" instead of "/". See if you get a
cookie there. Then, if you have a browser that allows you to inspect
session cookies (mozilla is good for this), check the path of your
session cook
Hi
I am experiencing a problem with session tracking when using Apache 2.0.39's
mod_proxy module to connect to my Tomcat 4.0.3 instance.
I have a servlet which checks to see if a session exists, and if not,
creates a new session.
When testing on a standalone instance of Tomcat, all works as exp
Rajeev Bakhru typed the following on 03:24 PM 1/17/2001 -0500
>On the login jsp page in the application, I used a servlet and created a
>session with
>HttpSession session = req.getSession(true)
...
>Then on this page (b) , I used
> and passes the same variable again to
>the another page (c).
Che
I am having problem in tracking sessions.
On the login jsp page in the application, I used a servlet and created a
session with
HttpSession session = req.getSession(true)
then after sucessful login it goes to the next jsp page say(b)
and passess some variables to this page as a hidden variable.
