|
Posted by Jerry Stuckle on 04/17/06 01:18
Bruno wrote:
> Agreed - A cookie on two.com should not be accessible by one.com.
>
> I want the cookie on two.com to be accessible by two.com inside a frame
> originating on a page at one.com.
>
> But, when the two.com page sets a cookie, and chains another page in two.com
> (within the frameset defined at one.com) the cookie values are not
> accessible under IE as they are for all other browsers.
>
> Now, if I go into the IE privacy setting, click 'override cookie handling',
> and ensure 'always allow third party cookies' is checked the application
> will work in a frame, otherwise it will only work under IE if it is in a
> separate browser window (i.e. being the 'primary' site)
>
> I'm just not happy about having to give instructions to the masses telling
> them to adjust their cookie settings under IE. And as far as I'm concerned,
> site two.com using a site two.com cookie should not be an unrealistic
> thing...
>
Bruno,
Just read this thread
That makes sense. The main page is one.com, so two.com is a third-party for
that page. Unlike when the page is directly loaded from two.com, where there is
no other party involved.
Sounds like IE is doing exactly what it should. Other than telling the user to
change their browser settings, there isn't much you can do.
One of the reasons for this setting, btw, is to limit ad tracking. Third part
ads would set cookies on one page and be able to read them on another page (the
ads would be originated at the same domain so this works).
BTW - please don't top post. This group uses bottom posting as a standard.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
[Back to original message]
|