<?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"
	>
<channel>
	<title>Comments on: consuming web services / crafting webrequests using ssl where the cert is expired or otherwise hosed</title>
	<atom:link href="http://mhinze.com/archive/consuming-web-services-crafting-webrequests-using-ssl-where-the-cert-is-expired-or-otherwise-hosed/feed/" rel="self" type="application/rss+xml" />
	<link>http://mhinze.com/archive/consuming-web-services-crafting-webrequests-using-ssl-where-the-cert-is-expired-or-otherwise-hosed/</link>
	<description>this is an archive of the old blog, ended 6/16/08</description>
	<pubDate>Mon, 15 Mar 2010 19:07:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Bob On Development &#187; Accepting a Flaky Certificate When Doing an SSL POST</title>
		<link>http://mhinze.com/archive/consuming-web-services-crafting-webrequests-using-ssl-where-the-cert-is-expired-or-otherwise-hosed/#comment-1555</link>
		<dc:creator>Bob On Development &#187; Accepting a Flaky Certificate When Doing an SSL POST</dc:creator>
		<pubDate>Sat, 14 Apr 2007 19:37:21 +0000</pubDate>
		<guid isPermaLink="false">http://mhinze.com/consuming-web-services-crafting-webrequests-using-ssl-where-the-cert-is-expired-or-otherwise-hosed/#comment-1555</guid>
		<description>[...] Update:  I ran across the .NET 2.0 solution to this issue here: [...]</description>
		<content:encoded><![CDATA[<p>[...] Update:  I ran across the .NET 2.0 solution to this issue here: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
