提问者:小点点

异常处理中间件和页面


我是中间件概念的新手,目前正在努力寻找合适的方法来处理我的MVC核心项目中的异常。

我想发生的是捕获异常,记录异常,然后将用户发送到带有消息的友好错误页面。起初,我试图在中间件中管理所有这些,但意识到我可能做得不正确。

因此,如果我希望这个流程发生,我应该同时使用我的异常记录中间件和应用程序吗?UseExceptionHandler("/Error ")以便中间件将异常重新抛出到页面?如果是这样,如何在错误页面中获得异常的详细信息?我想首先拦截的异常处理机制应该是Configure中的最后一个,这是正确的吗?

我发现的所有例子都严格处理HTTP状态代码错误,如404;我希望处理实际的异常(及其子类)。这样,在我的视图页面中,我可以在适当的时候抛出我自己的异常(例如,如果一个视图的必填字段为空。)

启动.cs片段:

public void Configure(IApplicationBuilder app, IHostingEnvironment env, 
                      ILoggerFactory loggerFactory, LoanDbContext context) {
    loggerFactory.AddConsole(Configuration.GetSection("Logging"));
    loggerFactory.AddDebug();

    app.UseStatusCodePages();
    if (env.IsDevelopment() || env.IsEnvironment("qa")) {
        app.UseDeveloperExceptionPage();
        app.UseBrowserLink();
    } else {
        app.UseExceptionHandler("/Error");
    }
    app.UseMiddleware<MyExceptionHandler>(loggerFactory);
    // ... rest of Configure is irrelevant to this issue

MyExceptionHandler.cs

using Microsoft.AspNetCore.Http;
using Microsoft.EntityFrameworkCore;
using Microsoft.Extensions.Logging;
using System;
using System.Data.SqlClient;
using System.Threading.Tasks;

namespace MyCompany.MyProject.Helpers
{
    /// <summary>
    /// A custom Exception Handler Middleware which can be re-used in other projects.
    /// </summary>
    public sealed class MyExceptionHandler
    {
        private readonly RequestDelegate _next;
        private readonly ILogger _logger;

        public MyExceptionHandler(RequestDelegate next, ILoggerFactory loggerFactory) {
            _next = next;
            _logger = loggerFactory.CreateLogger<MyExceptionHandler>();
        }

        public async Task Invoke(HttpContext context) {
            try {
                await _next(context);
            } catch (Exception ex) {
                HandleException(ex);
            }
        }

        // I realize this function looks pointless, but it will have more meat to it eventually.
        public void HandleException(Exception ex) {
            if (ex is ArgumentException argEx) {
                _logger.LogError(0, argEx, argEx.Message);
            } else if (ex is InvalidOperationException ioEx) {
                _logger.LogError(0, ioEx, "An Invalid Operation Exception occurred. This is usually caused by a database call that expects "
                    + "one result, but receives none or more than one.");
            } else if (ex is SqlException sqlEx) {
                _logger.LogError(0, sqlEx, $"A SQL database exception occurred. Error Number {sqlEx.Number}");
            } else if (ex is NullReferenceException nullEx) {
                _logger.LogError(0, nullEx, $"A Null Reference Exception occurred. Source: {nullEx.Source}.");
            } else if (ex is DbUpdateConcurrencyException dbEx) {
                _logger.LogError(0, dbEx, "A database error occurred while trying to update your item. This is usually due to someone else modifying the item since you loaded it.");
            } else {
                _logger.LogError(0, ex, "An unhandled exception has occurred.")
            }
        }
    }
}

共1个答案

匿名用户

我应该同时使用我的异常记录中间件和< code >应用程序吗?UseExceptionHandler("/Error ")以便中间件向页面重新抛出异常?

没问题.

只使用你的例子的一个片段。

public async Task Invoke(HttpContext context) {
    try {
        await _next(context);
    } catch (Exception ex) {
        HandleException(ex);
         // re -throw the original exception
         // after logging the information
        throw;
    }
}

上面的代码将在记录错误后重新抛出原始错误,以便管道中的其他处理程序能够捕捉到它并进行开箱即用的处理。

ASP.NET 核心中的源错误处理

如何在错误页面中获取异常详细信息?

使用IExceptionHandlerPathFeature获取异常和路径

public IActionResult Error()
{
    // Get the details of the exception that occurred
    var exceptionFeature = HttpContext.Features.Get<IExceptionHandlerPathFeature>();

    if (exceptionFeature != null)
    {
        // Get which route the exception occurred at
        string routeWhereExceptionOccurred = exceptionFeature.Path;

        // Get the exception that occurred
        Exception exceptionThatOccurred = exceptionFeature.Error;

        // TODO: Do something with the exception
        // Log it with Serilog?
        // Send an e-mail, text, fax, or carrier pidgeon?  Maybe all of the above?
        // Whatever you do, be careful to catch any exceptions, otherwise you'll end up with a blank page and throwing a 500
    }

    return View();
}

使用IExceptionHandlerPathFeature在ASP.NET核心中添加全局错误处理和日志记录

在上面的示例中,他们提到在视图中进行日志记录,但您应该已经在自定义处理程序中完成了。

在渲染错误视图时,请特别注意这条小注释。

无论你做什么,都要小心捕捉任何异常,否则你最终会得到一个空白页并抛出 500

通过插入管道,您可以避免重新发明框架已经提供的现成功能,同时还可以管理跨领域的问题。

相关问题