blocks|key|193411|text|回答我自己的问题，这是不可能的！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|193412|处理所有导致内部服务器错误的异常似乎是Web应该具备的基本能力，所以我向微软申请了一个Web+的全局错误处理程序|offset|length|style|BOLD|193413|https://aspnetwebstack.codeplex.com/workitem/1001|193414|如果您同意，请转到该链接并为其投票！|193415|同时，优秀的文章ASP.NET+Web+API+Exception+Handling展示了几种不同的方法来捕获几种不同类别的错误。它比正常情况下更复杂，而且它不能捕获所有内部服务器错误，但它是目前可用的最好方法。|193416|更新：全局错误处理现在已经实现，并在每晚的构建中可用！它将在ASP.NET+MVCV5.1中发布。下面是它的工作原理：https://aspnetwebstack.codeplex.com/wikipage?title=Global%2520Error%2520Handling|193417|entityMap|0|LINK|mutability|MUTABLE|url|1|http://weblogs.asp.net/fredriknormen/archive/2012/06/11/asp-net-web-api-exception-handling.aspx|2|https://aspnetwebstack.codeplex.com/wikipage?title=Global%2520Error%2520Handling^0|0|1C|8|0|0|1D|0|1D|0|0|0|I|0|0|2Y|8|Y|1|0|0|3R|1N|24|2|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@$D|17|E|18|1|19]]|A|$]]|$1|J|3|K|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@$D|1G|E|1H|1|1I]]|A|$]]|$1|N|3|O|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@$D|1M|E|1N|1|1O]]|A|$]]|$1|P|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|I]]|W|$5|S|T|U|A|$V|X]]|Y|$5|S|T|U|A|$V|Z]]]]

To answer my own question, this isn't possible!

Handling all exceptions that cause internal server errors seems like a basic capability Web API should have, so I have put in a request with Microsoft for a Global error handler for Web API:

<a href="https://aspnetwebstack.codeplex.com/workitem/1001">https://aspnetwebstack.codeplex.com/workitem/1001</a>

If you agree, go to that link and vote for it!

In the meantime, the excellent article <a href="http://weblogs.asp.net/fredriknormen/archive/2012/06/11/asp-net-web-api-exception-handling.aspx">ASP.NET Web API Exception Handling</a> shows a few different ways to catch a few different categories of error. It's more complicated than it should be, and it doesn't catch all interal server errors, but it's the best approach available today.

Update: Global error handling is now implemented and available in the nightly builds! It will be released in ASP.NET MVC v5.1. Here's how it will work: <a href="https://aspnetwebstack.codeplex.com/wikipage?title=Global%20Error%20Handling">https://aspnetwebstack.codeplex.com/wikipage?title=Global%20Error%20Handling</a>

blocks|key|2812742|text|现在，在WebAPI+2.1中可以做到这一点(参见What's+New)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2812743|创建IExceptionLogger的一个或多个实现。例如：|2812744|public+class+TraceExceptionLogger+:+ExceptionLogger
{
++++public+override+void+Log(ExceptionLoggerContext+context)
++++{
++++++++Trace.TraceError(context.ExceptionContext.Exception.ToString());
++++}
}|code-block|syntax|javascript|2812745|然后在配置回调中使用应用程序的HttpConfiguration进行注册，如下所示：|2812746|config.Services.Add(typeof(IExceptionLogger),+new+TraceExceptionLogger());|2812747|或者直接：|2812748|GlobalConfiguration.Configuration.Services.Add(typeof(IExceptionLogger),+new+TraceExceptionLogger());|2812749|entityMap|0|LINK|mutability|MUTABLE|url|http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-21#global-error^0|P|A|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|17|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|19|8|@]|9|@]|C|$I|J]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

This is now possible with WebAPI 2.1 (see the <a href="http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-21#global-error">What's New</a>):

Create one or more implementations of IExceptionLogger. For example:

<pre><code>public class TraceExceptionLogger : ExceptionLogger
{
 public override void Log(ExceptionLoggerContext context)
 {
 Trace.TraceError(context.ExceptionContext.Exception.ToString());
 }
}
</code></pre>

Then register with your application's HttpConfiguration, inside a config callback like so:

<pre><code>config.Services.Add(typeof(IExceptionLogger), new TraceExceptionLogger());
</code></pre>

or directly:

<pre><code>GlobalConfiguration.Configuration.Services.Add(typeof(IExceptionLogger), new TraceExceptionLogger());
</code></pre>

blocks|key|3025424|text|您还可以通过实现IExceptionHandler接口(或继承ExceptionHandler基类)来创建全局异常处理程序。在所有已注册的IExceptionLogger之后，它将是执行链中最后一个被调用的|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3025425|3025426|+IExceptionHandler处理来自所有控制器的所有未处理的异常。这是列表中的最后一个。如果发生异常，将首先调用IExceptionLogger，然后调用控制器ExceptionFilters，如果仍未处理，则调用IExceptionHandler实现。|blockquote|3025427|3025428|3025429|public+class+OopsExceptionHandler+:+ExceptionHandler
{
++++public+override+void+HandleCore(ExceptionHandlerContext+context)
++++{
++++++++context.Result+=+new+TextPlainErrorResult
++++++++{
++++++++++++Request+=+context.ExceptionContext.Request,
++++++++++++Content+=+"Oops!+Sorry!+Something+went+wrong."++++++++
++++++++};
++++}

++++private+class+TextPlainErrorResult+:+IHttpActionResult
++++{
++++++++public+HttpRequestMessage+Request+{+get;+set;+}

++++++++public+string+Content+{+get;+set;+}

++++++++public+Task<HttpResponseMessage>+ExecuteAsync(CancellationToken+cancellationToken)
++++++++{
++++++++++++HttpResponseMessage+response+=+
+++++++++++++++++++++++++++++new+HttpResponseMessage(HttpStatusCode.InternalServerError);
++++++++++++response.Content+=+new+StringContent(Content);
++++++++++++response.RequestMessage+=+Request;
++++++++++++return+Task.FromResult(response);
++++++++}
++++}
}|code-block|syntax|javascript|3025430|更多关于here的信息。|3025431|entityMap|0|LINK|mutability|MUTABLE|url|http://www.asp.net/web-api/overview/error-handling/web-api-global-error-handling^0|8|H|V|G|1X|G|0|0|0|0|0|0|4|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|17|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|18|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|19|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1B|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|S|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

You can also create a global exception handler by implementing the <code>IExceptionHandler</code> interface (or inherit the <code>ExceptionHandler</code> base class). It will be the last to be called in the execution chain, after all registered <code>IExceptionLogger</code>:

<blockquote>
 The IExceptionHandler handles all unhandled exceptions from all
 controllers. This is the last in the list. If an exception occurs, the
 IExceptionLogger will be called first, then the controller
 ExceptionFilters and if still unhandled, the IExceptionHandler
 implementation.
</blockquote>

<pre><code>public class OopsExceptionHandler : ExceptionHandler
{
 public override void HandleCore(ExceptionHandlerContext context)
 {
 context.Result = new TextPlainErrorResult
 {
 Request = context.ExceptionContext.Request,
 Content = "Oops! Sorry! Something went wrong." 
 };
 }

 private class TextPlainErrorResult : IHttpActionResult
 {
 public HttpRequestMessage Request { get; set; }

 public string Content { get; set; }

 public Task&lt;HttpResponseMessage&gt; ExecuteAsync(CancellationToken cancellationToken)
 {
 HttpResponseMessage response = 
 new HttpResponseMessage(HttpStatusCode.InternalServerError);
 response.Content = new StringContent(Content);
 response.RequestMessage = Request;
 return Task.FromResult(response);
 }
 }
}
</code></pre>

More on that <a href="http://www.asp.net/web-api/overview/error-handling/web-api-global-error-handling" rel="noreferrer">here</a>.

blocks|key|3025467|text|Yuval的答案是定制对Web+API捕获的未处理异常的响应，而不是用于日志记录，如链接的page所示。有关详细信息，请参阅页面上的何时使用部分。记录器始终被调用，但处理程序仅在可以发送响应时才被调用。简而言之，使用logger来记录日志，使用处理程序来定制响应。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3025468|顺便说一句，我使用的是assembly+v5.2.3，而ExceptionHandler类没有HandleCore方法。我认为与之相当的是Handle。然而，简单地对ExceptionHandler进行子类化(就像Yuval的答案一样)是行不通的。在我的例子中，我必须实现IExceptionHandler，如下所示。|style|CODE|3025469|internal+class+OopsExceptionHandler+:+IExceptionHandler
{
++++private+readonly+IExceptionHandler+_innerHandler;

++++public+OopsExceptionHandler+(IExceptionHandler+innerHandler)
++++{
++++++++if+(innerHandler+==+null)
++++++++++++throw+new+ArgumentNullException(nameof(innerHandler));

++++++++_innerHandler+=+innerHandler;
++++}

++++public+IExceptionHandler+InnerHandler
++++{
++++++++get+{+return+_innerHandler;+}
++++}

++++public+Task+HandleAsync(ExceptionHandlerContext+context,+CancellationToken+cancellationToken)
++++{
++++++++Handle(context);

++++++++return+Task.FromResult<object>(null);
++++}

++++public+void+Handle(ExceptionHandlerContext+context)
++++{
++++++++//+Create+your+own+custom+result+here...
++++++++//+In+dev,+you+might+want+to+null+out+the+result
++++++++//+to+display+the+YSOD.
++++++++//+context.Result+=+null;
++++++++context.Result+=+new+InternalServerErrorResult(context.Request);
++++}
}|code-block|syntax|javascript|3025470|请注意，与记录器不同，您可以通过替换默认处理程序来注册处理程序，而不是添加。|3025471|config.Services.Replace(typeof(IExceptionHandler),
++++new+OopsExceptionHandler(config.Services.GetExceptionHandler()));|3025472|entityMap|0|LINK|mutability|MUTABLE|url|http://www.asp.net/web-api/overview/error-handling/web-api-global-error-handling|1|https://stackoverflow.com/a/21382651/2028733|2|https://github.com/ASP-NET-MVC/aspnetwebstack/blob/master/src/System.Web.Http/ExceptionHandling/ExceptionHandler.cs^0|19|4|0|30|6|1|0|S|G|1B|A|1X|6|2B|G|3S|H|S|G|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]|$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|6|7|19|8|@$A|1A|B|1B|F|G]|$A|1C|B|1D|F|G]|$A|1E|B|1F|F|G]|$A|1G|B|1H|F|G]|$A|1I|B|1J|F|G]]|9|@$A|1K|B|1L|1|1M]]|C|$]]|$1|H|3|I|5|J|7|1N|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1O|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1P|8|@]|9|@]|C|$K|L]]|$1|Q|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]|10|$5|T|U|V|C|$W|11]]]]

The Yuval's answer is for customizing responses to unhandled exceptions caught by Web API, not for logging, as noted on the linked <a href="http://www.asp.net/web-api/overview/error-handling/web-api-global-error-handling" rel="noreferrer">page</a>. Refer to the When to Use section on the page for details. The logger is always called but the handler is called only when a response can be sent. In short, use the <a href="https://stackoverflow.com/a/21382651/2028733">logger</a> to log and the handler to customize the response.

By the way, I am using assembly v5.2.3 and the <a href="https://github.com/ASP-NET-MVC/aspnetwebstack/blob/master/src/System.Web.Http/ExceptionHandling/ExceptionHandler.cs" rel="noreferrer"><code>ExceptionHandler</code></a> class does not have the <code>HandleCore</code> method. The equivalent, I think, is <code>Handle</code>. However, simply subclassing <code>ExceptionHandler</code> (as in Yuval's answer) does not work. In my case, I have to implement <code>IExceptionHandler</code> as follows.

<pre><code>internal class OopsExceptionHandler : IExceptionHandler
{
 private readonly IExceptionHandler _innerHandler;

 public OopsExceptionHandler (IExceptionHandler innerHandler)
 {
 if (innerHandler == null)
 throw new ArgumentNullException(nameof(innerHandler));

 _innerHandler = innerHandler;
 }

 public IExceptionHandler InnerHandler
 {
 get { return _innerHandler; }
 }

 public Task HandleAsync(ExceptionHandlerContext context, CancellationToken cancellationToken)
 {
 Handle(context);

 return Task.FromResult&lt;object&gt;(null);
 }

 public void Handle(ExceptionHandlerContext context)
 {
 // Create your own custom result here...
 // In dev, you might want to null out the result
 // to display the YSOD.
 // context.Result = null;
 context.Result = new InternalServerErrorResult(context.Request);
 }
}
</code></pre>

Note that, unlike the logger, you register your handler by replacing the default handler, not adding.

<pre><code>config.Services.Replace(typeof(IExceptionHandler),
 new OopsExceptionHandler(config.Services.GetExceptionHandler()));
</code></pre>

blocks|key|3025528|text|您可能没有意识到现有的try-catch块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3025529|我认为我的新global.asax.Application_Error方法在遗留代码中没有一致地调用未处理的异常。|offset|length|style|CODE|3025530|然后，我在调用堆栈的中间发现了几个try-catch块，它们在异常文本上调用Response.Write。就是这样。将文本转储到屏幕上，然后终止异常。|3025531|所以异常正在被处理，但是这种处理没有做任何有用的事情。一旦我删除了那些try-catch块，异常就像预期的那样传播到Application_Error方法。|3025532|entityMap^0|0|6|T|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

You may have existing try-catch blocks that you're not aware of.

I thought my new <code>global.asax.Application_Error</code> method wasn't being consistently called for unhandled exceptions in our legacy code. 

Then I found a few try-catch blocks in the middle of the call stack that called Response.Write on the Exception text. That was it. Dumped the text on the screen then killed the exception stone dead.

So the exceptions were being handled, but the handling was doing nothing useful. Once I removed those try-catch blocks the exceptions propagated to the Application_Error method as expected.

How do I catch all unhandled exceptions that occur in ASP.NET Web Api so that I can log them?

So far I have tried:

<ul>
<li>Create and register an <a href="http://weblogs.asp.net/fredriknormen/archive/2012/06/11/asp-net-web-api-exception-handling.aspx"><code>ExceptionHandlingAttribute</code></a></li>
<li>Implement an <code>Application_Error</code> method in <code>Global.asax.cs</code></li>
<li>Subscribe to <code>AppDomain.CurrentDomain.UnhandledException</code></li>
<li>Subscribe to <code>TaskScheduler.UnobservedTaskException</code></li>
</ul>

The <code>ExceptionHandlingAttribute</code> successfully handles exceptions that are thrown within controller action methods and action filters, but other exceptions are not handled, for example:

<ul>
<li>Exceptions thrown when an <code>IQueryable</code> returned by an action method fails to execute</li>
<li>Exceptions thrown by a message handler (i.e. <code>HttpConfiguration.MessageHandlers</code>)</li>
<li>Exceptions thrown when creating a controller instance</li>
</ul>

Basically, if an exception is going to cause a 500 Internal Server Error to be returned to the client, I want it logged. Implementing <code>Application_Error</code> did this job well in Web Forms and MVC - what can I use in Web Api?

catch all unhandled exceptions in ASP.NET Web Api

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如何捕获ASP.NET Web中发生的所有未处理的异常，以便记录这些异常？到目前为止，我已经尝试过：在Global.asax.csSubscribe to AppDomain.CurrentDomain.UnhandledExceptionSubscribe to TaskScheduler.UnobservedTas...

问捕获ASP.NET Web Api中所有未处理的异常
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问捕获ASP.NET Web Api中所有未处理的异常EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问捕获ASP.NET Web Api中所有未处理的异常
EN