【问题标题】:C# DotNet Core Middleware Wrap ResponseC# DotNet Core 中间件包装响应
【发布时间】:2018-04-21 05:42:03
【问题描述】:

我有一个简单的控制器动作,如下所示:

    public Task<IEnumerable<Data>> GetData()
    {
        IEnumerable<Data> data = new List<Data>();
        return data;
    }

我希望能够从中间件中检查返回值,以便 JSON 看起来像

{
  "data": [
  ],
  "apiVersion": "1.2",
  "otherInfoHere": "here"
}

所以我的有效载荷总是在data 内。我知道我可以在控制器级别做到这一点,但我不想在每一个动作上都这样做。我宁愿在中间件中一劳永逸。

这是我的中间件的一个例子:

public class NormalResponseWrapper
{
    private readonly RequestDelegate next;

    public NormalResponseWrapper(RequestDelegate next)
    {
        this.next = next;
    }

    public async Task Invoke(HttpContext context)
    {                
        var obj = context;
        // DO something to get return value from obj
        // Create payload and set data to return value

        await context.Response.WriteAsync(/*RETURN NEW PAYLOAD HERE*/);
    }

有什么想法吗?

现在得到了价值,但返回它已经太晚了

        try
        {
            using (var memStream = new MemoryStream())
            {
                context.Response.Body = memStream;
                await next(context);
                memStream.Position = 0;
                object responseBody = new StreamReader(memStream).ReadToEnd();
                memStream.Position = 0;
                await memStream.CopyToAsync(originalBody);
                // By now it is to late, above line sets the value that is going to be returned
                await context.Response.WriteAsync(new BaseResponse() { data = responseBody }.toJson());
            }

        }
        finally
        {
            context.Response.Body = originalBody;
        }

【问题讨论】:

  • 看看这个,看看它是否适用stackoverflow.com/questions/43403941/…
  • 这样我就得到了数据,但是当我操作它并尝试返回它时为时已晚
  • 这有内存问题的风险吗?
  • 与大型有效负载相关的正常问题没有任何问题。请注意,这种方法不适用于流式传输。
  • 这是迄今为止我发现的最佳实现的链接:vmsdurano.com/…

标签: c# .net-core middleware httpcontext


【解决方案1】:

查看 cmets 以了解您可以采取哪些措施来包装响应。

public async Task Invoke(HttpContext context) {
    //Hold on to original body for downstream calls
    Stream originalBody = context.Response.Body;
    try {
        string responseBody = null;
        using (var memStream = new MemoryStream()) {
            //Replace stream for upstream calls.
            context.Response.Body = memStream;
            //continue up the pipeline
            await next(context);
            //back from upstream call.
            //memory stream now hold the response data
            //reset position to read data stored in response stream
            memStream.Position = 0;
            responseBody = new StreamReader(memStream).ReadToEnd();
        }//dispose of previous memory stream.
        //lets convert responseBody to something we can use
        var data = JsonConvert.DeserializeObject(responseBody);
        //create your wrapper response and convert to JSON
        var json = new BaseResponse() { 
            data = data, 
            apiVersion = "1.2",
            otherInfoHere = "here"
        }.toJson();
        //convert json to a stream
        var buffer = Encoding.UTF8.GetBytes(json);
        using(var output = new MemoryStream(buffer)) {
            await output.CopyToAsync(originalBody);
        }//dispose of output stream
    } finally {
        //and finally, reset the stream for downstream calls
        context.Response.Body = originalBody;
    }
} 

【讨论】:

  • 我认为这种方法很糟糕,因为它是在 HTTP 级别上处理的,如果您决定使用其他序列化格式(如 XML 或 protobuf),它会中断。我会在其他地方做这样的事情
  • 每次都必须反序列化响应。这种包装应该在序列化之前发生
【解决方案2】:

在 .NET Core 3.1 或 .NET 5 中

  1. 创建您的响应信封对象。示例:

    internal class ResponseEnvelope<T>
    {
      public T Data { set; get; }
      public string ApiVersion { set; get; }
      public string OtherInfoHere { set; get; }
    }
    
  2. 从 ObjectResultExecutor 派生一个类

    internal class ResponseEnvelopeResultExecutor : ObjectResultExecutor
    {
     public ResponseEnvelopeResultExecutor(OutputFormatterSelector formatterSelector, IHttpResponseStreamWriterFactory writerFactory, ILoggerFactory loggerFactory, IOptions<MvcOptions> mvcOptions) : base(formatterSelector, writerFactory, loggerFactory, mvcOptions)
     {
     }
    
     public override Task ExecuteAsync(ActionContext context, ObjectResult result)
     {
         var response = new ResponseEnvelope<object>();
         response.Data = result.Value;
         response.ApiVersion = "v1";
         response.OtherInfoHere = "OtherInfo";
    
         TypeCode typeCode = Type.GetTypeCode(result.Value.GetType());
         if (typeCode == TypeCode.Object)
              result.Value = response;
    
         return base.ExecuteAsync(context, result);
      }
    }
    
  3. 像注入DI一样

    public void ConfigureServices(IServiceCollection services)
     {
         services.AddSingleton<IActionResultExecutor<ObjectResult>, ResponseEnvelopeResultExecutor>();
    

并且回复应该有一个信封。 这不适用于原始类型。

【讨论】:

  • 除了更简单之外,它也不会受到上面@Konrad 指出的假定媒体类型等问题的影响。
  • 你能解释一下你的代码吗?你为什么这样做? TypeCode typeCode = Type.GetTypeCode(result.Value.GetType()); if (typeCode == TypeCode.Object)
猜你喜欢
  • 1970-01-01
  • 2019-04-12
  • 1970-01-01
  • 1970-01-01
  • 2019-03-26
  • 1970-01-01
  • 2018-01-07
  • 2022-01-09
  • 1970-01-01
相关资源
最近更新 更多