<?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: Silverlight HTTP Networking Stack &#8211; Part 3 (Configuring a Cross Domain Policy File)</title>
	<atom:link href="http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/feed/" rel="self" type="application/rss+xml" />
	<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/</link>
	<description>karen corby's fabulous blog</description>
	<lastBuildDate>Tue, 16 Feb 2010 20:10:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Recent Links: ASP.NET, ASP.NET AJAX, ASP.NET MVC, Silverlight &#171; Tad Wang&#8217;s Weblog</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-2480</link>
		<dc:creator>Recent Links: ASP.NET, ASP.NET AJAX, ASP.NET MVC, Silverlight &#171; Tad Wang&#8217;s Weblog</dc:creator>
		<pubDate>Fri, 18 Dec 2009 20:26:21 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-2480</guid>
		<description>[...] HTTP Networking Stack (Part 1), (Part 2), (Part 3): Karen Corby from the Silverlight team has a great three part blog series that talks about the new [...]</description>
		<content:encoded><![CDATA[<p>[...] HTTP Networking Stack (Part 1), (Part 2), (Part 3): Karen Corby from the Silverlight team has a great three part blog series that talks about the new [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arthur</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-678</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Mon, 22 Sep 2008 07:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-678</guid>
		<description>crossdomain.xml not working:

I have created a simple service and hosted it on my local IIS.
when i try to access it from another site i get 404 error.
ClientAccessPolicy.xml works great, but if i remove it an use only crossdomain.xml it doesn&#039;t.
Why is that?

I have used you format of crossdomain.xml and the one posted at http://msdn.microsoft.com/en-us/library/cc645049(VS.95).aspx#cross_domain_policy</description>
		<content:encoded><![CDATA[<p>crossdomain.xml not working:</p>
<p>I have created a simple service and hosted it on my local IIS.<br />
when i try to access it from another site i get 404 error.<br />
ClientAccessPolicy.xml works great, but if i remove it an use only crossdomain.xml it doesn&#8217;t.<br />
Why is that?</p>
<p>I have used you format of crossdomain.xml and the one posted at <a href="http://msdn.microsoft.com/en-us/library/cc645049(VS.95).aspx#cross_domain_policy" rel="nofollow">http://msdn.microsoft.com/en-us/library/cc645049(VS.95).aspx#cross_domain_policy</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-677</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Tue, 17 Jun 2008 17:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-677</guid>
		<description>Excellent catch.. yes, that is a typo.  It should be in the &lt;allow-from&gt; tag.  I&#039;ve updated this post.</description>
		<content:encoded><![CDATA[<p>Excellent catch.. yes, that is a typo.  It should be in the <allow -from> tag.  I&#8217;ve updated this post.</allow></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Muston</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-674</link>
		<dc:creator>Paul Muston</dc:creator>
		<pubDate>Tue, 17 Jun 2008 15:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-674</guid>
		<description>In example 1 you have the http-request-headers=&quot;Content-Type&quot; in  element - is this correct?
http://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx shows it in the  element. Typo - you are also self closing the  element.</description>
		<content:encoded><![CDATA[<p>In example 1 you have the http-request-headers=&#8221;Content-Type&#8221; in  element &#8211; is this correct?<br />
<a href="http://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx</a> shows it in the  element. Typo &#8211; you are also self closing the  element.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-676</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 11 Jun 2008 06:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-676</guid>
		<description>I would like to see an code example using YouTube or at least know why it cannot be created.</description>
		<content:encoded><![CDATA[<p>I would like to see an code example using YouTube or at least know why it cannot be created.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Masaki(JP)</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-675</link>
		<dc:creator>Masaki(JP)</dc:creator>
		<pubDate>Wed, 21 May 2008 01:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-675</guid>
		<description>Great!
Can I translate to Japanese, and carry to my blog?</description>
		<content:encoded><![CDATA[<p>Great!<br />
Can I translate to Japanese, and carry to my blog?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: srinath</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-672</link>
		<dc:creator>srinath</dc:creator>
		<pubDate>Wed, 30 Apr 2008 09:58:48 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-672</guid>
		<description>Great article! Thanks.
Minor bug: It should be &quot;uri&quot; in example 2 (&quot;i&quot; missing).
Question: Is there a way to explictly deny access to a subpath while giving access to a path.</description>
		<content:encoded><![CDATA[<p>Great article! Thanks.<br />
Minor bug: It should be &#8220;uri&#8221; in example 2 (&#8220;i&#8221; missing).<br />
Question: Is there a way to explictly deny access to a subpath while giving access to a path.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Amundsen</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-671</link>
		<dc:creator>Mike Amundsen</dc:creator>
		<pubDate>Tue, 29 Apr 2008 14:20:30 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-671</guid>
		<description>I understand that challenges and appreciate the initial work done heere to get cross-domain requests up and running. However, in-message authentication is - by nature - a security risk. Until HTTPS and Basic/Digest is properly supported, it is much wiser to simply *not* expose private content via cross-domain requests.</description>
		<content:encoded><![CDATA[<p>I understand that challenges and appreciate the initial work done heere to get cross-domain requests up and running. However, in-message authentication is &#8211; by nature &#8211; a security risk. Until HTTPS and Basic/Digest is properly supported, it is much wiser to simply *not* expose private content via cross-domain requests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Bromberg</title>
		<link>http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/comment-page-1/#comment-673</link>
		<dc:creator>Peter Bromberg</dc:creator>
		<pubDate>Thu, 24 Apr 2008 00:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://scorbs.com/2008/04/22/silverlight-http-networking-stack-part-3-configuring-a-cross-domain-policy-file/#comment-673</guid>
		<description>This is great stuff! But why do people insist on posting sample code with line numbers at the left? If i want to copy the code, then I have to go and remove all the line numbers before I can use it!</description>
		<content:encoded><![CDATA[<p>This is great stuff! But why do people insist on posting sample code with line numbers at the left? If i want to copy the code, then I have to go and remove all the line numbers before I can use it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
