I'm not sure if that problem is connected to mod_jk2. There are four ways for session tracking. SSL, hidden form fields, url rewriting or cookies. Tomcat can use certain methods mostly transparent if necessary e.g. if cookies are disabled then url rewriting is in use. I guess your session info should be lost whenever you use static html files at least if you don't allow cookies. Why not take jsp pages instead as they maintain the session info. As far as I know there's no safe way to mix jsp/servlet sessions with static ressources. Only with cookies I could imagine that it stays persistent, but I guess you get into trouble because cookies are set in the https headers before any response is generated, thus they can never be set by any included page.
mech > -----Original Message----- > From: Matt Sales [mailto:[EMAIL PROTECTED]] > Sent: Mittwoch, 4. Dezember 2002 20:19 > To: Tomcat Users List > Subject: TC/Apache session tracking > > > Hello, > I've got a problem tracking sessions from Tomcat 4.1.12/Apache 2.0.40. > > I can do all of the regular session stuff within Tomcat, but > when I include a tomcat page in a static html page, sessions > are not persisted. I'm using mod_jk2 to connect the two... > > ex: > <!--#include virtual="/tcapp/servlet/myServlet" --> > > I get the output from myServlet, but every pass of the > session.isNew() > method returns true. > > The sessions don't persist even if I include two servlets > from the same .shtml page. This can't be right... Is there > a setting I'm missing? > > Thanks in advance, > Matt > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
