Hi The reazon is because the seesion is created with info from the call: example: IP address, Port Etc, and Tomcat has to create a new session because the info is different, I'm being trying to find a solution for this problem, but still I'm working on that. I'll keep you posted...or if you find a solution please forward that to me
Thanks --- Amir S <[EMAIL PROTECTED]> wrote: > Hi All, > > I have a Jakarta 5.0.28. > When entering the tomcat first > https://127.0.0.1/a.jsp and then > http://127.0.0.1/b.jsp > The sessionID changes?! > In the revise (http://127.0.0.1/b.jsp and then > https://127.0.0.1/a.jsp) > order it does not, why is that?! > How can I fix it? > Please note that the different is in the HTTPS and > HTTP order. > > Regards, > Amir S > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: > users@tomcat.apache.org > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
