Owin Middleware vs ExceptionHandler vs HttpMessageHandler(DelegatingHandler)

Question

请有人知道如何在asp.net Web API 2.1中跟随三个模块一起工作

• Owin中间件
• HttpMessageHandler(或DelegatingHandler)
• 的ExceptionHandler

我所试图做的是开发和Web API,它将会提供恒定的格式JSON数据,意味着如果实际数据

{"Id":1,"UserName":"abc","Email":"abc@xyz.com"}

然后我喜欢把json作为

{__d:{"Id":1,"UserName":"abc","Email":"abc@xyz.com"}, code:200, somekey: "somevalue"}

为此,我尝试使用自定义ActionFilterAttribute但我觉得(仍未确认)在代码遇到异常的情况下,这无法提供类似的格式化数据

请建议我最好的方向.

这是我的自定义属性的简短代码片段.另外建议我是自定义属性是有益的

[AttributeUsage(AttributeTargets.Method | AttributeTargets.Class, Inherited = true, AllowMultiple = false)]
public class ResponseNormalizationAttribute : ActionFilterAttribute
{
    public override void OnActionExecuted(HttpActionExecutedContext actionExecutedContext)
    {
            base.OnActionExecuted(actionExecutedContext);
            var response = actionExecutedContext.Response;
            object contentValue;
            if (response.TryGetContentValue(out contentValue))
            {
                var nval = new { data=contentValue, status = 200 };


                var newResponse = new HttpResponseMessage { Content = new ObjectContent(nval.GetType(), nval, new JsonMediaTypeFormatter()) };
                newResponse.Content.Headers.ContentType = new MediaTypeHeaderValue("application/json");
                actionContext.Response = newResponse;
            }
     }
}

Answer 1

如果您不使用 Owin 中间件，则可以全局包装所有响应，以便它将使用委托处理程序返回常量格式 json 数据。

编写一个继承自 DelegatingHandler 的自定义处理程序：

public class ApiResponseHandler : DelegatingHandler
{
    protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        var response = await base.SendAsync(request, cancellationToken);

        return BuildResponse(request, response);
    }

    private static HttpResponseMessage BuildResponse(HttpRequestMessage request, HttpResponseMessage response)
    {
        object content;
        string errorMessage = null;

        if (response.TryGetContentValue(out content) && !response.IsSuccessStatusCode)
        {
            HttpError error = content as HttpError;

            if (error != null)
            {
                content = null;
                errorMessage = error.Message;
            }
        }

        var newResponse = request.CreateResponse(response.StatusCode, new ApiResponse((int)response.StatusCode, content, errorMessage));

        foreach (var header in response.Headers)
        {
            newResponse.Headers.Add(header.Key, header.Value);
        }

        return newResponse;
    }
}

//ApiResponse is your constant json response
public class ApiResponse
{

    public ApiResponse(int statusCode, object content, string errorMsg)
    {
        Code = statusCode;
        Content = content;
        Error = errorMsg;
        Id = Guid.NewGuid().ToString();
    }

    public string Error { get; set; }

    //your actual data is mapped to the Content property
    public object Content { get; set; }
    public int Code { get; private set; }
    public string Id { get; set; }
}

在以下位置注册处理程序WebApiConfig.cs：

    public static void Register(HttpConfiguration config)
    {
        // Web API routes
        config.MapHttpAttributeRoutes();
        ...

        config.MessageHandlers.Add(new ApiResponseHandler());

        config.Routes.MapHttpRoute(
            name: "DefaultApi",
            routeTemplate: "{controller}/{id}",
            defaults: new { id = RouteParameter.Optional }
        );

        ...
    }

我在 SO 中发布了类似的答案，但这是在 .NET Core 中并作为 OWIN 中间件实现（因为 DelegatingHandler 已在 .NET Core 中消失）。 如何包装 Web API 响应（在 .net core 中）以保持一致性？