即使允许几乎所有内容,ASP.NET 5/Core/vNext CORS 也无法正常工作

ASP.NET 5/Core/vNext CORS not working even if allowing pretty much everything(即使允许几乎所有内容,ASP.NET 5/Core/vNext CORS 也无法正常工作)

本文介绍了即使允许几乎所有内容,ASP.NET 5/Core/vNext CORS 也无法正常工作的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个 ASP.NET 5 Web API(好吧,无论如何现在都是 MVC)后端,我正在使用

  • 对于实际的 POST 请求(这个没有通过):
  • 解决方案

    问题实际上在于处理 POST 请求的操作中存在异常,正如 Norgerman 所说,默认异常处理程序清除了 CORS 标头.

    I have a ASP.NET 5 Web API (Well, MVC now anyway) back-end which I am consuming in with the axios library in my JS app.

    My CORS config in MVC is the following:

    public void ConfigureServices(IServiceCollection services)
    {
          services.AddMvc();
          services.AddCors();
    } 
    
    
    public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
    { 
          app.UseCors(builder => {
              builder.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader();
          });
    }
    

    So in other words, I should be allowing every request possible. However, while this fixed preflight requests, a POST requests still gets rejected (I can see it executes on the server, but there's no header in the response so it results in a client side error).

    Does anyone have any ideas why this wouldn't work ?

    These are the headers that are returned by the MVC api:

    • For the OPTIONS preflight (this one passes):
    • For the actual POST request (this one does NOT pass):

    解决方案

    The problem was actually in the fact that there was an exception in the action processing the POST request and as Norgerman mentioned, the default exception handler cleared the CORS headers.

    这篇关于即使允许几乎所有内容,ASP.NET 5/Core/vNext CORS 也无法正常工作的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

    本文标题为:即使允许几乎所有内容,ASP.NET 5/Core/vNext CORS 也无法正常工作

    基础教程推荐