Forum Moderators: open

Message Too Old, No Replies

P3P and third party cookies.

IE 6 causing headaches.

         

ritch_b

2:15 pm on Aug 21, 2003 (gmt 0)

10+ Year Member



I'll gladly confess that this P3P malarky is a new one to me & having come across a problem this morning, I've spent a large proportion of the day unsuccessfully seeking a solution.

I'm working on www.widget.com - a frames site for a client. On the site's a feature that searches www.bigwidget.com and displays the results in an i-frame within the client site.

Once the results are returned, IE 6's privacy policy icon appears stating that the session cookie from www.bigwidget.com has been blocked - this prevents the user from navigating back and forth through the search results.

Dropping the IE security settings from default (medium) to low solves the problem, but isn't the ideal, obviously.

How does one go about adding sorting this via the privacy policy files, if indeed it can be?

The cookie itself is pretty simple - session only, anonymous and used to track which results have been clicked on.

The information on W3's site is a bit overkill and I've had no joy with the IBM P3P Policy Editor with regards to this particular problem. Any help appreciated.

Cheers,

R.

msr986

5:28 am on Aug 22, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



you need to create a privacy policy for IE6 to allow the third party cookie.

You say "no joy" with the IBM P3P Policy Editor, what went wrong?

What aspect of P3P are you having trouble with?

digitalghost

5:33 am on Aug 22, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Adding a link to the p3p file via a tag or adding an HTTP header with the compact policy usually sorts the third party cookie issue.

msr986

5:50 am on Aug 22, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I just remembered I had this flagged:

[webmasterworld.com...]

Hope this helps!

ritch_b

9:56 am on Aug 22, 2003 (gmt 0)

10+ Year Member



Cheers peeps!

It's the compact policy in the external page header that's been causing problems - or to be precise, the lack of it.

I've mocked a page up at this end, added the compact policy to the page header via .HTACCESS with success & been in touch with the network guys responsible for the external page who reckon all will be sorted for Tuesday...fingers crossed!

Thanks again.

R.