On 13/04/06, Sam Varshavchik <[EMAIL PROTECTED]> wrote: > Browsers will reject cookies that a domain will try to set for a different > domain. > > But in this case, you are setting a cookie for your own domain. The old > saying goes: you break it, you get to pick up the pieces.
Fair enough. Though I was under the impression that subdomain.domain.com can set cookies under domain.com. I just looked at mail.google.com, it sets 3 out of 10 or so cookies under mail.google.com, the rest are all under google.com. In my case, I have siteminder (and securid) enabled for reports.mydomain.com and also somethingelse.mydomain.com, so asking siteminder to change its cookie domain sort of beats the purpose of single sign-on. In a hypothetical situation, I'd have mydomain.com/webmail for sqwebmail, mydomain.com/reports for siteminder and so on. But I'm wondering in such a case, I can legitimately have siteminder setting cookies under mydomain.com and sqwebmail crashing? Binand ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
