UseStatusCodePagesWithReExecute with UseStaticFiles results in wrong status code (200 OK)

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have a few static files, one for each status code. I want to display those when an error code happens. I’m using a combination of UseStatusCodePagesWithReExecute and UseStaticFiles. However the StaticFilesMiddleware will replace the existing status code with 200, so now any error page is served with 200 OK instead of the actual status code.

app.UseStatusCodePagesWithReExecute("/Errors/{0}.html");
app.UseStaticFiles();

Expected Behavior

The status code should reflect the actual error.

Steps To Reproduce

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
app.UseStatusCodePagesWithReExecute("/error.html");
app.UseStaticFiles();
app.MapGet("/", async context => { context.Response.StatusCode = 500; });
app.Run();

Exceptions (if any)

No response

.NET Version

6.0.200

Anything else?

No response

[Tratcher]

Yes, we should do both. Make individual components behave better, but store the status code in the feature for when something doesn’t. I’ll have to find the MVC example, it’s somewhere in ActionResults.

[Tratcher]

Reopening based on feedback from https://github.com/dotnet/AspNetCore.Docs/issues/26935.

We could improve this by saving the status code on IStatusCodeReExecuteFeature so that it is available in case the response generator overwrites it, like in StaticFile’s OnPrepareResponse. We could also avoid setting default response status codes (200) in static files and mvc.