dotnet / dotnet/aspnetcore

CORS header not being set for internal server error response

Open
#22,281 6 comments 7 reactions 0 assignees View on GitHub
affected-very-few area-middleware enhancement feature-cors investigate Needs: Design Priority:2 severity-nice-to-have triage-focus
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

For internal server error, there are no access-control-* headers in the response. As far as I know
[this issue](https://github.com/dotnet/aspnetcore/issues/2378) should be fixed since ASP.NET Core 2.2.

Here is my CORS configuration:
``` C#
services.AddCors(options =>
{
options.AddPolicy(name: "AllowedOrigins",
policyBuilder =>
{
var urls = Configuration.GetSection("Host:AllowedOrigins").Get>();
policyBuilder.WithOrigins(urls.ToArray())
.AllowAnyMethod()
.AllowAnyHeader()
.SetIsOriginAllowed((host) => true)
.AllowCredentials();
});
});
```
And in `Configure` method :

```C#
app.UseRouting();

app.UseCors("AllowedOrigins");
app.UseAuthentication();
app.UseAuthorization();

app.UseEndpoints(endpoints =>
{
endpoints.MapControllers();
});
```
### Further technical details
```
- ASP.NET Core version: 3.1

.NET Core SDK (reflecting any global.json):
Version: 3.1.202
Commit: 6ea70c8dca

Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.202\

Host (useful for support):
Version: 3.1.4
Commit: 0c2e69caa6

.NET Core SDKs installed:
1.0.0 [C:\Program Files\dotnet\sdk]
2.1.802 [C:\Program Files\dotnet\sdk]
2.2.402 [C:\Program Files\dotnet\sdk]
3.1.200 [C:\Program Files\dotnet\sdk]
3.1.202 [C:\Program Files\dotnet\sdk]
- Visual Studio 15.6
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.