3 ms·
>P3P is a curious animal. This was a requirement to have IE6 accept third party cookies from your site.
by brobinson 8y ago
>P3P is a curious animal.
This was a requirement to have IE6 accept third party cookies from your site.
- synhare 8y agoThis part of the article really threw me off. Someone writing an article on HTTP headers for a major CDN has never had to deal with IE6?
- barneygale 8y agoAre people really still dealing with IE6? I gave up web dev almost a decade ago and it's disturbing to hear that IE6 is still an issue!
- shakna 8y agoEnterprise. A lot of Enterprise applications are required for work, and require very old, very stubborn browsers. Most emulations don't work. You need the old stuff (IE), for the old applications to work, and as long as they can force it to, they won't update said old application. I've even had to touch systems which required IE 4 in the last few years, from before Trident became the rendering engine.
- zbentley 8y agoHealthcare and government (US). So, so very many systems are on IE6. So, so very many websites only work correctly/fully when end users are on that platform. Until you've had to support code distributed by the US federal gov't and watch the percentages of users hitting your site from XP (or earlier) UAs rise to the double digits, you have not known sadness.
- gboudrias 8y agoAlso all of China or so I was told about a year ago.
- LordHeini 8y agoNot only ie6 but ie11 on windows 7 as well. Windows 10 ie11 does not care about p3p. Have fun debugging your ajax stuff on that one if those stupid headers fail. Luckyly one can just fill that p3p header with garbage and the ie will just gobble it up be happy. Go figure...