Microsoft accuses Google of it a privacyprotocol in Internet Explorer to work. The questionable accusation follows on the news that Google is a loophole in the privacy protections of the Safari browser has been compromised.
In a blog post on MSDN writes Microsoft that Google is a privacyprotocol of the W3C bypasses. The post is placed as a result of the news that Google is the privacy of Safari excluded. Google revealed in a creative way, third party cookies, while Safari by default blocks.
The post Microsoft is about third party cookies. Internet Explorer only allows certain third party cookies as a website, the p3p protocol of the World Wide Web Consortium supports, by sending a http-header in which the privacy policy is indicated. Sites that promise no personal information to any third party by locks and an opt-out offer may still third party cookies. That are often used by advertisers.
According to Microsoft, manipulates Google, the p3p protocol to identifying third party cookies, namely by an invalid p3p header to send. Internet Explorer is in an invalid p3p header anyway third party cookies. That claim is true on paper; a p3p header belongs according to the specification, to consist of specified keywords by a browser can be read out, while that of Google is composed of a disclaimer and a url. As a result, the p3p header is not valid and cookies are accepted.
On the claim of Microsoft may, however, be afgedongen. So, Google is one of the many websites that the p3p protocol is not support. Also Facebook, in which Microsoft has a minority stake, to ignore the protocol. In his p3p-header indicates to Google that too literally:
P3P => CP=”This is not a P3P policy!
See http://www.google.com/support/accounts/bin/answer.py?
hl=en&answer=151657 for more info.”
The url referenced writes Google that sometimes it is cookies from another domain need a user to authenticate, for example, in the Google+buttons. Must fact personal information to be sent. The p3p protocol, which dates back to 2002, does not take it into account, writes Google.
Additionally, Internet Explorer is the only commonly used browser that is p3p-protocol supports. That the protocol is not actually some level of protection, have known for years. Mozilla removed the support for p3p in 2003 and also IBM, that the protocol was originally developed, has against the protocol spoken. Because of the poor support the W3C decided to further develop the protocol to stop.
Google spokesperson Rachel Whetstone let in a statement to know that the p3p specification does not take into account new functionality for which cookies are used, such as the like buttons of Facebook. Whetstone does the protocol as a feature of Internet Explorer that actually is not supported.
Who anyway third party cookies want to block in Internet Explorer, can in new versions, the do not track option is enable. Microsoft says, to examine whether the implementation of the p3p specification may change, so that the sites with invalid p3p headers is still impossible for third party to place cookies. Internet Explorer supports p3p since version 6.