I read the docs long ago, I've had to clean the cookies programmatically several times for several people.
We had a a site that was accessible as www.xxxxxx.com and xxxxxx.com, the cookies for xxxxxx.com come back for www but not the other way around. So I got into using domain names in cookies or just realizing that it will cause headaches. I don't remember where I read all about it, but there are issues with using domain = ".xxxxxx.com" vs "xxxxxx.com" and a big issue with just letting it default to the domain and path of the page that hands out the cookie! On 4/18/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Ⓙⓐⓚⓔ schrieb: > Setting a path and a domain is required for knowing exactly where the > cookies are going to apply. > > Sloppy cookies can be fun, but someone will have to clean up the > crumbs sooner or later! Can you point to a good resource or explain a bit about properly setting path and domain for cookies? -- Jörn Zaefferer http://bassistance.de
-- Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
