Azure Functions v4独立模式自定义授权中间件返回500异常

问题描述 #

在.NET独立进程模式的Azure Functions App v4中，尝试通过自定义特性和中间件简化JWT授权逻辑校验令牌，但遇到问题：当中间件尝试通过FunctionContext返回HTTP响应时，函数抛出500内部服务器错误。简化测试场景（移除特性后让中间件直接返回401）后，问题依旧。调试时代码执行正常，但几秒后收到500错误。

代码示例 #

授权中间件代码 #

internal class AuthorizationMiddleware : IFunctionsWorkerMiddleware
{
    public async Task Invoke(FunctionContext context, FunctionExecutionDelegate next)
    {
        try
        {
            var httpRequestData = await context.GetHttpRequestDataAsync();
            if ((httpRequestData == null))
            {
                Console.WriteLine("Request is NULL, calling next()");
                await next(context);
                return;
            }

            var httpResponse = httpRequestData!.CreateResponse(HttpStatusCode.Unauthorized);
            await httpResponse.WriteStringAsync("unauthorized");
            context.GetInvocationResult().Value = httpResponse;
            return;
        }
        catch (Exception ex)
        {
            System.Diagnostics.Debug.WriteLine($"Error in AuthorizationMiddleware: {ex.Message}");
            throw;
        }
    }
}

程序启动代码 #

private static void Main(string[] args)
{
    var builder = FunctionsApplication.CreateBuilder(args);

    builder.UseMiddleware<ExceptionHandlingMiddleware>();
    builder.UseMiddleware<AuthorizationMiddleware>();

    builder.ConfigureFunctionsWebApplication();

    builder.Build().Run();
}

环境与依赖包 #

• 操作系统：Windows 10
• 开发工具：Visual Studio 2022
• 框架：.NET 8
• Azure Functions版本：v4
• 依赖包：

<PackageReference Include="Microsoft.Azure.Functions.Worker" Version="2.0.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.2.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" Version="2.0.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="2.0.0" />
<PackageReference Include="Microsoft.Azure.WebJobs" Version="3.0.41" />

异常信息 #

添加异常捕获中间件后，捕获的异常表面为null，但查看内部细节发现：

System.Exception.InnerExceptionPrefix: "--->"
System.Exception._COMPlusExceptionCode : -532462766

解决建议 #

• 适配AspNetCore集成的响应处理方式：由于使用了Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore包，函数基于AspNetCore管道运行，不能通过FunctionContext.GetInvocationResult()设置响应，应直接获取AspNetCore的HttpContext来操作响应。修改后的中间件代码如下：

  internal class AuthorizationMiddleware : IFunctionsWorkerMiddleware
  {
      public async Task Invoke(FunctionContext context, FunctionExecutionDelegate next)
      {
          try
          {
              if (context.TryGetHttpContext(out var httpContext))
              {
                  httpContext.Response.StatusCode = StatusCodes.Status401Unauthorized;
                  await httpContext.Response.WriteAsync("unauthorized");
                  await httpContext.Response.Body.FlushAsync();
                  return;
              }
  
              await next(context);
          }
          catch (Exception ex)
          {
              System.Diagnostics.Debug.WriteLine($"Error in AuthorizationMiddleware: {ex.Message}");
              throw;
          }
      }
  }
  

• 调整中间件注册顺序：ConfigureFunctionsWebApplication()需要先调用，它会初始化AspNetCore管道，之后再注册自定义中间件，确保中间件能正确接入AspNetCore的请求流程：

  private static void Main(string[] args)
  {
      var builder = FunctionsApplication.CreateBuilder(args);
  
      builder.ConfigureFunctionsWebApplication();
  
      builder.UseMiddleware<ExceptionHandlingMiddleware>();
      builder.UseMiddleware<AuthorizationMiddleware>();
  
      builder.Build().Run();
  }
  

• 移除不必要的依赖包：Microsoft.Azure.WebJobs是针对Azure Functions In-Process模式的包，在独立进程模式下无需引入，移除该包可避免版本冲突和潜在的对象生命周期问题。

• 排查对象释放异常：_COMPlusExceptionCode : -532462766对应COR_E_OBJECTDISPOSED（对象已被释放），原代码中直接设置InvocationResult.Value的方式与AspNetCore集成不兼容，导致响应对象被提前释放，按照上述方式修改响应处理逻辑即可解决该问题。

内容的提问来源于stack exchange，提问作者John McArthur