The cookie domain determines under what domains the browser will send the cookie. The cookie domain is matched against the Host header.
http://en.wikipedia.org/wiki/HTTP_cookie#Domain_and_Path On Feb 18, 2013, at 12:31 PM, Mike Vogt <[email protected]> wrote: > Hi all, > I'm attempting to use session data from our production site to carry over to > an archive site of pretty much the same data without requiring the user to > log in again. I'm pretty sure the issue is the difference in the 2 domain > names. I was wondering if I could set the session cookie domain to a value > shared by the 2 sites so that our session checking code in the archive > wouldn't reject a user transferred to it from our production server. Is that > what the SESSION COOKIE DOMAIN setting is for? If I can't do this, I'll > probably scrap the idea of an archive server. > > TIA, > MV > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://list.aparajitaworld.com/listinfo/active4d-dev > Archives: http://active4d-nabble.aparajitaworld.com/ Regards, Aparajita _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
