Wednesday, June 22, 2016

ASP.NET Core 1.0 RC2 Status Code Handling

[Please note that this post discusses the topic in the context of ASP.NET Core 1.0 RC2]

In this post let’s see how we can easily handle Status Codes (for instance 404: Not Found) in an ASP.NET Core 1.0 web application.

By the framework we are given with 3 options.
  • app.UseStatusCodePages();
  • app.UseStatusCodePagesWithRedirects()
  • app.UseStatusCodePagesWithReExecute()

Let’s go through each of these by creating a sample application. From Visual Studio, create a new project and select ASP.NET Core Web Application (.NET Core) and from the next page select Web Application.
ASP.NET Core Web Application (.NET Core)
Once the project is created, open up Startup.cs and navigate to Configure method where you configure the Middleware for your ASP.NET Core Web Application.

There on the IApplicationBuilder, you can see the following three extension methods for handling status codes.
Extension Methods for Handling Status Codes
The easy way to generate 404 error is after running the application, navigate to a view which doesn’t exist. Now let’s see how we can handle 404 with each of these extension methods.

1. UseStatusCodePages

This is the most simple among all three options. Just modify the Configure method adding the following.

Now if you generate a 404 by running the application, this is what you will get.

You can specify couple of options over there like modifying the response.
app.UseStatusCodePages("text/plain", "It's a : {0}");


2. UseStatusCodePagesWithRedirects

You can  use this method to specify a separate page (with either relative or absolute URL) as follows.
And here you need to add 404.html page inside a folder named “errorpages” under “wwwroot”.

<!DOCTYPE html>
    <meta charset="utf-8" />
    <h1> Not found. </h1>
And now if you generate a 404, this is the output.


And here if you take a closer look at the URL, you can see that it has been changed because the request is redirected to that particular page.

3. UseStatusCodePagesWithReExecute

When you use this approach what will happen is the request will be re executed (what ever the middleware which is defined after this line) and that’s using the given path.
For instance here the request will try to navigate to StatusCode controller and invoke the specified action. We don’t have a MVC controller named StatusCodeController and let’s just add it inside Controllers folder.
public class StatusCodeController : Controller
    public IActionResult Index(int code)
        return View(code);
And let’s add the respective View for this action. For that let’s create a folder named StatusCode inside Views folder. There let’s add a MVC View Page named Index.cshtml.
Now let’s run the application and generate a 404.

Here you can notice that there was no URL redirection has been done.

So that's about it. Do explore ASP.NET Core 1.0.

Happy Coding.


1 comment:

  1. Thank you so much for your post! I found your solution very helpful.