<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Obtaining more information from an HttpException</title><link>http://blogs.msdn.com/b/tmarq/archive/2009/03/10/obtaining-more-information-from-an-httpexception.aspx</link><description>ASP.NET throws HttpException for numerous types of errors, making it difficult to determine exactly what went wrong programmatically. You can parse the error message, but the message can be localized, and therefore parsing it can be non-trivial. There</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Obtaining more information from an HttpException</title><link>http://blogs.msdn.com/b/tmarq/archive/2009/03/10/obtaining-more-information-from-an-httpexception.aspx#9531882</link><pubDate>Sun, 05 Apr 2009 16:37:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9531882</guid><dc:creator>stic</dc:creator><description>&lt;p&gt;Well done - it was really unhandy to use WebEventCode &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9531882" width="1" height="1"&gt;</description></item></channel></rss>