<?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 for ByteCyclist</title>
	<atom:link href="http://www.bytecyclist.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bytecyclist.com</link>
	<description>A site made of bytes by a cyclist.</description>
	<pubDate>Tue, 06 Jan 2009 20:24:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Bytecyclist dot com by Ellie</title>
		<link>http://www.bytecyclist.com/2008/09/03/bytecyclist-dot-com/comment-page-1/#comment-5</link>
		<dc:creator>Ellie</dc:creator>
		<pubDate>Tue, 28 Oct 2008 05:02:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytecyclist.com/?p=4#comment-5</guid>
		<description>People should read this.</description>
		<content:encoded><![CDATA[<p>People should read this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Frustrating IIS7 Configuration 500 Error by Bill Staples</title>
		<link>http://www.bytecyclist.com/2008/09/22/frustrating-iis7-configuration-500-error/comment-page-1/#comment-4</link>
		<dc:creator>Bill Staples</dc:creator>
		<pubDate>Tue, 23 Sep 2008 01:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytecyclist.com/?p=19#comment-4</guid>
		<description>Sorry you ran into this...unfortunately the error is by design.  Now that IIS relies on web.config for configuration, if IIS is unable to read a config file (which may contain authentication / authorization information, etc.) it returns a server 500 error.  For remote users, the error is generic as one would not want details about the application or server sent back to would-be hackers.  For local users, you should actually see a very detailed error message showing you the invalid XML error, including line number and config snippet.</description>
		<content:encoded><![CDATA[<p>Sorry you ran into this&#8230;unfortunately the error is by design.  Now that IIS relies on web.config for configuration, if IIS is unable to read a config file (which may contain authentication / authorization information, etc.) it returns a server 500 error.  For remote users, the error is generic as one would not want details about the application or server sent back to would-be hackers.  For local users, you should actually see a very detailed error message showing you the invalid XML error, including line number and config snippet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Frustrating IIS7 Configuration 500 Error by Frustrating IIS7 Configuration 500 Error &#124; Legal Webmastering</title>
		<link>http://www.bytecyclist.com/2008/09/22/frustrating-iis7-configuration-500-error/comment-page-1/#comment-3</link>
		<dc:creator>Frustrating IIS7 Configuration 500 Error &#124; Legal Webmastering</dc:creator>
		<pubDate>Mon, 22 Sep 2008 19:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytecyclist.com/?p=19#comment-3</guid>
		<description>[...] here: Frustrating IIS7 Configuration 500 Error     Posted in Web Hosting on Sep 22nd, 2008, 1:13 [...]</description>
		<content:encoded><![CDATA[<p>[...] here: Frustrating IIS7 Configuration 500 Error     Posted in Web Hosting on Sep 22nd, 2008, 1:13 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Black Betty Snowboard Video by Cariann</title>
		<link>http://www.bytecyclist.com/2008/09/04/black-betty-snowboard-video/comment-page-1/#comment-2</link>
		<dc:creator>Cariann</dc:creator>
		<pubDate>Sat, 06 Sep 2008 19:21:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.bytecyclist.com/?p=14#comment-2</guid>
		<description>Holy cow!  Kyle, that was awesome.  Very nice job and WAY entertaining!</description>
		<content:encoded><![CDATA[<p>Holy cow!  Kyle, that was awesome.  Very nice job and WAY entertaining!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
