tomcat sessions are not only specific to your domain, but also to the actual webapp.
tomcat per spec can not share cookies across webapps, even less across domain. why dont you set your own cookie, and set the domain to myserver.com, and then keep track of it yourself Filip > -----Original Message----- > From: Troy A. Griffitts [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 4:40 PM > To: [EMAIL PROTECTED] > Subject: session between domains > > > Hey guys. I have a standard site, say: > > http://mysite.myserver.com > > And eventually the user gets to a place where we'll need to jump them to > something like: > > https://secure.myserver.com > > to take their credit card information. I lose my session when doing > this. Both URLs point to the same server and are served by the same > webapp-- I can shop the whole site on https://secure.myserver.com/, but > I can't make the jump. > > I'm guessing it probably has something to do with my jsessionid being > stored as a cookie. I was wondering if I could force the > ';jsessionid=xxxxxxxx...' to the url or something. > > > Otherwise, how does one usually handle such a common thing with tomcat? > > -Troy. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
