asp.net-core - 在 .Net Core 2.2 中将 HttpResponseMessage 作为 IActionResult 返回的正确方法

标签 asp.net-core .net-core asp.net-core-2.0 asp.net-core-webapi coreclr

在 .Net Core 2.2 中。我正在创建一个 API Controller ,根据负载将请求路由到另一个 Http 端点。

  [Route("api/v1")]
  public class RoutesController : Controller
  {
      [HttpPost]
      [Route("routes")]
      public async Task<IActionResult> Routes([FromBody]JObject request)
      {
                 
        var httpClient = new HttpClient();

        // here based on request httpCLient will make `POST` or `GET` or `PUT` request
        // and returns `Task<HttpResponseMessage>`. Lets assume its making `GET` 
        // call

       Task<HttpResponseMessage> response = await
         httpClient.GetAsync(request["resource"]);
            
       /*  ??? what is the correct way to return response as `IActionResult`*/
      }        
  }

基于SO发布我可以做到这一点

        return StatusCode((int)response.StatusCode, response);

但是我不确定将 HttpResponseMessage 作为 ObjectResult 发送是正确的方式。

我还想确保内容协商能够发挥作用。

2022 年 7 月 25 日更新
更新了正确答案

最佳答案

public class HttpResponseMessageResult : IActionResult
{
    private readonly HttpResponseMessage _responseMessage;

    public HttpResponseMessageResult(HttpResponseMessage responseMessage)
    {
        _responseMessage = responseMessage; // could add throw if null
    }

    public async Task ExecuteResultAsync(ActionContext context)
    {
        var response = context.HttpContext.Response;


        if (_responseMessage == null)
        {
            var message = "Response message cannot be null";

            throw new InvalidOperationException(message);
        }

        using (_responseMessage)
        {
            response.StatusCode = (int)_responseMessage.StatusCode;

            var responseFeature = context.HttpContext.Features.Get<IHttpResponseFeature>();
            if (responseFeature != null)
            {
                responseFeature.ReasonPhrase = _responseMessage.ReasonPhrase;
            }

            var responseHeaders = _responseMessage.Headers;

            // Ignore the Transfer-Encoding header if it is just "chunked".
            // We let the host decide about whether the response should be chunked or not.
            if (responseHeaders.TransferEncodingChunked == true &&
                responseHeaders.TransferEncoding.Count == 1)
            {
                responseHeaders.TransferEncoding.Clear();
            }

            foreach (var header in responseHeaders)
            {
                response.Headers.Append(header.Key, header.Value.ToArray());
            }

            if (_responseMessage.Content != null)
            {
                var contentHeaders = _responseMessage.Content.Headers;

                // Copy the response content headers only after ensuring they are complete.
                // We ask for Content-Length first because HttpContent lazily computes this
                // and only afterwards writes the value into the content headers.
                var unused = contentHeaders.ContentLength;

                foreach (var header in contentHeaders)
                {
                    response.Headers.Append(header.Key, header.Value.ToArray());
                }

                await _responseMessage.Content.CopyToAsync(response.Body);
            }
        }
    }

关于asp.net-core - 在 .Net Core 2.2 中将 HttpResponseMessage 作为 IActionResult 返回的正确方法,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/54136488/

相关文章:

c# - 如何将文件复制到 Azure Function bin 文件夹中?

c# - onChange 事件未触发 Blazor InputSelect

c# - 当我在 Visual Studio 中创建 .net core 项目时,我没有获得 TreeView

c# - 找不到包 'Microsoft.AspNet.WebApi.Client' .Net Core 2.2 的编译库位置

c# - 创建编译时未知类型的 ImmutableList

c# - 为什么 IHttpContextAccessor.HttpContext 不正确

c# - SignalR 测试 - 如何在新版本的 SignalR for ASP.NET Core 2 中模拟组

c# - 保持前端 Angular 5 和后端 Web API 代码分离的简单方法?

c# - 让 HomeController 继承自具有 session 属性的 BaseController

c# - 尝试在窗口服务中托管 .NET Core 2.1 Web 应用程序会创建 dll 而不是 exe