<?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: Custom errors and error detail policy in ASP.NET Web API</title>
	<atom:link href="http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/</link>
	<description>Strong opinions, weakly held</description>
	<lastBuildDate>Sun, 19 May 2013 03:22:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Matt Scully</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-5620</link>
		<dc:creator>Matt Scully</dc:creator>
		<pubDate>Wed, 06 Mar 2013 18:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-5620</guid>
		<description>I came across this post trying to track down how to get exception details in Web API responses.  I thought it worth noting that, as of the official Web API release, this behavior was changed such that Web API _does_ default to the customErrors ASP.NET configuration.  If the Web API IncludeErrorDetailPolicy is set to Default, then the ASP.NET customErrors setting is used.  If customErrors is not set, the default will be LocalOnly.

See the &quot;official documentation&quot; (the code) here:

http://aspnetwebstack.codeplex.com/SourceControl/changeset/view/7825aa4e5b67#src/System.Web.Http/HttpConfiguration.cs
(Search for &quot;ShouldIncludeErrorDetail&quot;)</description>
		<content:encoded><![CDATA[<p>I came across this post trying to track down how to get exception details in Web API responses.  I thought it worth noting that, as of the official Web API release, this behavior was changed such that Web API _does_ default to the customErrors ASP.NET configuration.  If the Web API IncludeErrorDetailPolicy is set to Default, then the ASP.NET customErrors setting is used.  If customErrors is not set, the default will be LocalOnly.</p>
<p>See the &#8220;official documentation&#8221; (the code) here:</p>
<p><a href="http://aspnetwebstack.codeplex.com/SourceControl/changeset/view/7825aa4e5b67#src/System.Web.Http/HttpConfiguration.cs" rel="nofollow">http://aspnetwebstack.codeplex.com/SourceControl/changeset/view/7825aa4e5b67#src/System.Web.Http/HttpConfiguration.cs</a><br />
(Search for &#8220;ShouldIncludeErrorDetail&#8221;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4584</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 03 May 2012 12:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4584</guid>
		<description>Ha, that&#039;s much easier than my way, which was unlocking each status code at a time. Thanks!</description>
		<content:encoded><![CDATA[<p>Ha, that&#8217;s much easier than my way, which was unlocking each status code at a time. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Ove S. Olsen</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4581</link>
		<dc:creator>Jan Ove S. Olsen</dc:creator>
		<pubDate>Thu, 03 May 2012 08:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4581</guid>
		<description>Also, when hosting  ASP.NET WebAPI  in IIS, add the following to web.config to makes IIS not eat the body of your custom error responses.


    
        
    


If you&#039;re running IIS7/7.5 on a &quot;security hardened&quot; server, you&#039;ll need to run the following commands to &quot;unlock&quot; that config section:

cd C:WindowsSystem32inetsrv

appcmd unlock config /section:httpErrors

See details here: http://stackoverflow.com/questions/2345532/turn-iis7-http-error-handling-off

Regards, 
Jan Ove</description>
		<content:encoded><![CDATA[<p>Also, when hosting  ASP.NET WebAPI  in IIS, add the following to web.config to makes IIS not eat the body of your custom error responses.</p>
<p>If you&#8217;re running IIS7/7.5 on a &#8220;security hardened&#8221; server, you&#8217;ll need to run the following commands to &#8220;unlock&#8221; that config section:</p>
<p>cd C:WindowsSystem32inetsrv</p>
<p>appcmd unlock config /section:httpErrors</p>
<p>See details here: http://stackoverflow.com/questions/2345532/turn-iis7-http-error-handling-off</p>
<p>Regards, <br />
Jan Ove</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jalpesh Vadgama</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4575</link>
		<dc:creator>Jalpesh Vadgama</dc:creator>
		<pubDate>Wed, 02 May 2012 15:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4575</guid>
		<description>Nice work!! Would love to see more post from you on asp.net mvc 4.0</description>
		<content:encoded><![CDATA[<p>Nice work!! Would love to see more post from you on asp.net mvc 4.0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Another Tiny Contribution to WebApiContrib &#124; Headspring</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4564</link>
		<dc:creator>Another Tiny Contribution to WebApiContrib &#124; Headspring</dc:creator>
		<pubDate>Mon, 30 Apr 2012 18:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4564</guid>
		<description>[...] went ahead and took Jimmy’s blog post and turned it into code so it could be used straight from NuGet. If you are ever wanting to give [...]</description>
		<content:encoded><![CDATA[<p>[...] went ahead and took Jimmy’s blog post and turned it into code so it could be used straight from NuGet. If you are ever wanting to give [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4558</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 20 Apr 2012 15:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4558</guid>
		<description>Ha, weird that it was closed. I added a comment with some more links.</description>
		<content:encoded><![CDATA[<p>Ha, weird that it was closed. I added a comment with some more links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Hansen</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4557</link>
		<dc:creator>Martin Hansen</dc:creator>
		<pubDate>Fri, 20 Apr 2012 15:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4557</guid>
		<description>Thanks for answering the problem I had here: http://stackoverflow.com/questions/10243754/asp-net-web-api-returns-non-descriptive-error-500 </description>
		<content:encoded><![CDATA[<p>Thanks for answering the problem I had here: http://stackoverflow.com/questions/10243754/asp-net-web-api-returns-non-descriptive-error-500 </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy Bogard</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4556</link>
		<dc:creator>Jimmy Bogard</dc:creator>
		<pubDate>Fri, 20 Apr 2012 13:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4556</guid>
		<description>We thought about it, and will likely put that in place. But for quick debugging, it was confusing that this setting just didn&#039;t work.</description>
		<content:encoded><![CDATA[<p>We thought about it, and will likely put that in place. But for quick debugging, it was confusing that this setting just didn&#8217;t work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheRedCircuit</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4555</link>
		<dc:creator>TheRedCircuit</dc:creator>
		<pubDate>Fri, 20 Apr 2012 01:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4555</guid>
		<description>I was thinking, would it be easier to use elmah?</description>
		<content:encoded><![CDATA[<p>I was thinking, would it be easier to use elmah?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4554</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 19 Apr 2012 18:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/jimmybogard/2012/04/18/custom-errors-and-error-detail-policy-in-asp-net-web-api/#comment-4554</guid>
		<description>Will do!</description>
		<content:encoded><![CDATA[<p>Will do!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
