UseStatusCodePages Middleware Problem Resolved

Date Published: 01 December 2016

UseStatusCodePages Middleware Problem Resolved

If you’re trying to get the ASP.NET Core Status Code Pages middleware to work, but it just is ignored no matter what, one thing to check is the rest of your middleware pipeline. If you have middleware that is writing anything to the response, it will cause the status code pages middleware to be ignored. For example, the following middleware:

app.Use(async (context, next) =>  {   
    await next();

I had this set up in front of some other middleware to reduce duplication. I wanted to add support for 404 pages, so I added


which I expected to provide me with a simple 404 status code for any paths that weren’t mapped to middleware. However, it was never being triggered. Once I removed the common middleware that was setting the ContentType, the statuscodepages middleware started working as expected.

The reason for this is pointed out in the comments below. The StatusCodePages middleware checks to see if Response.ContentType is null or empty, and does nothing if ContentType has a value.

Steve Smith

About Ardalis

Software Architect

Steve is an experienced software architect and trainer, focusing on code quality and Domain-Driven Design with .NET.