|
Martijn Moeling
martijn at xs4us.nu
Tue Mar 9 05:22:42 EST 2010
Great to hear you got it working, Remember to give as much info as you have so you can be helped out more quickly. Indeed if you have multiple domains, you need to set the domain property of the cookie (do not set a cookie for .com .org etc since that will go out to a lot of websites!!!). Both are important for the browser to know wether to the cookie has to be in the headers of the request. say if you point your browser to www.yyy.com/test, the browser looks for cookies to fit. a cookie with domain .yyy.com and path / will fit, a cookie with domain www.yyy.com and path /test will fit too if you go to www2.yyy.com/ you will need a cookie with domain www2.yyy.com or .yyy.com and path set to "/" the browser will look for a "path" above the current path or current path so "/" will fit /test too, /test will fit for /test, /test/test2 but not for / Martijn On Mar 9, 2010, at 11:07 AM, K.Manikandan wrote: > >> Are the different webapps in different paths? >> besides c.domain, you also need/can set c.path = "/" (or whatever path, >> "/" might do the trick) >> >> since normally with the original Session.py is t's just adding >> PythonOption mod_python.session.application_path >> >> You need to set it to the same path in every index.py >> >> Martijn >> > > Atlast, We got what we needed. I was able to get the cookie of one webapp > from the other. Thanks a lot. > > Now, if we have two web applications in two different domains, then the > setting of cookie.domain will help right? We will try that. > > We will get back if we have any other problems... > > Regards, > Manikandan K > > > ----------------------------------------- > This email was sent using TCEMail Service. > Thiagarajar College of Engineering > Madurai-625 015, India >
|