MSIE Privacy Warning on Pro Domain
rdlugosz
Registered Users Posts: 277 Major grins
Hi folks - I'm working on my SM site to fix my IE Javascript issues and decided to grab a few screenshots of the "Privacy Warning" that MSIE users receive when visiting a SM site with a Pro Domain.
I believe the issue is related to the fact that the cookie comes from smugmug.com while the browser is pointed to gallery.rrdphoto.com - incidentally, moonriverphotography.com displays the same behavior.
Any chance this could be placed on the bug list for someone to look in to? "Privacy" warnings are never good to see on a site that someone may want to buy something from!! Below are a couple of screenies that illustrate the problem.
Here's a mention on MSDN of the P3P Privacy Policy that may be of reference.
One thought: Would it be possible to distribute the cookie from the custom domain instead of smugmug.com? That should remove the third-party cookie privacy issue.
My IE security settings (which I think are the default; I don't really use IE):
The Privacy Warning:
I believe the issue is related to the fact that the cookie comes from smugmug.com while the browser is pointed to gallery.rrdphoto.com - incidentally, moonriverphotography.com displays the same behavior.
Any chance this could be placed on the bug list for someone to look in to? "Privacy" warnings are never good to see on a site that someone may want to buy something from!! Below are a couple of screenies that illustrate the problem.
Here's a mention on MSDN of the P3P Privacy Policy that may be of reference.
One thought: Would it be possible to distribute the cookie from the custom domain instead of smugmug.com? That should remove the third-party cookie privacy issue.
My IE security settings (which I think are the default; I don't really use IE):
The Privacy Warning:
0
Comments
Portfolio • Workshops • Facebook • Twitter
Really? I just got one on IE 7, different computer, your site... see screen shot:
http://www.dgrin.com/showthread.php?t=65304
scwalter.smugmug.com
Interesting. So could we request that SmugMug add a "site wide P3P Policy" and fix this?
Either that or don't send that cookie in the first place on custom domains?