<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Cross Domain IFrame and Cookie Issues with IE7</title>
	<atom:link href="http://thefrontiergroup.com.au/blog/2009/02/cross-domain-iframe-and-cookie-issues-with-ie7/feed/" rel="self" type="application/rss+xml" />
	<link>http://thefrontiergroup.com.au/blog/2009/02/cross-domain-iframe-and-cookie-issues-with-ie7/</link>
	<description>Your peek inside the collective mind of The Frontier Group</description>
	<lastBuildDate>Wed, 21 Jul 2010 07:16:08 +0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aaron</title>
		<link>http://thefrontiergroup.com.au/blog/2009/02/cross-domain-iframe-and-cookie-issues-with-ie7/comment-page-1/#comment-178</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 05 Mar 2009 07:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://thefrontiergroup.com.au/blog/?p=336#comment-178</guid>
		<description>I&#039;m not sure what you mean? 

Essentially all this is saying is that you certify your website is built to handle any exploits that the browser is trying to protect it from. So it&#039;s up to you to either rely on browser security (not a great idea really) or to work on securing the site and explicitly say that the browser is free to expose your site to things it wouldn&#039;t normally allow. 

Check out the P3P spec and I think you&#039;ll see what I mean. In reality I think it only effects IE for the most part.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure what you mean? </p>
<p>Essentially all this is saying is that you certify your website is built to handle any exploits that the browser is trying to protect it from. So it&#8217;s up to you to either rely on browser security (not a great idea really) or to work on securing the site and explicitly say that the browser is free to expose your site to things it wouldn&#8217;t normally allow. </p>
<p>Check out the P3P spec and I think you&#8217;ll see what I mean. In reality I think it only effects IE for the most part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Khwab</title>
		<link>http://thefrontiergroup.com.au/blog/2009/02/cross-domain-iframe-and-cookie-issues-with-ie7/comment-page-1/#comment-168</link>
		<dc:creator>Khwab</dc:creator>
		<pubDate>Wed, 25 Feb 2009 13:48:28 +0000</pubDate>
		<guid isPermaLink="false">http://thefrontiergroup.com.au/blog/?p=336#comment-168</guid>
		<description>What about the security issues with it?</description>
		<content:encoded><![CDATA[<p>What about the security issues with it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
