Saturday 16 October 2010 8:30:29 am
Hi! I think I know partly why, earlier this week auth.ez.no was changed to use ".ez.no" as session cookie domain name to make some functionality work again after login was moved from ez.no to auth.ez.no.
This seems to trigger something in IE related to it's cookie handling, just found this page: http://blogs.msdn.com/b/ieinternals/archive/2009/08/20/wininet-ie-cookie-internals-faq.aspx EDIT: Looks like IE login have been broken since login was moved to auth.ez.no, anyone that can confirm that?
In worst case we're struck by IE's xx.yy cookie issue, not sure if it has been fixed or not (some page mentiones that it was fixed in IE6 sp1, but this page is more recent and does not mentione anything about that): http://stackoverflow.com/questions/1189638/internet-explorer-xx-yy-website-problem
Also several pages suggest that we have to use P3P: http://php.net/manual/en/function.setcookie.php#27819 Suggestions?
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|