Tel Map

Blog

302 Redirect VS 401 Unauthorized – ASP .NET 5 Identity

302 API Redirect Problem

If you make a request to a REST service and are not logged in, by default ASP .NET 5 Identity returns a 302 Redirect to login page. This is great if you are visiting the URL of a controller directly. If you make an Ajax request to a specific REST API and are not logged in however, you are also redirected to the login page and instead of the content of the API you will get the content of the login page itself. Probably without even noticing it right away.

So in instance of API calls I would prefer a 401 Unauthorized status code, e.g. $http requests using AngularJS. Here only the Ajax call itself gets redirected, but the URL of the browser remains the same. This means you won’t see that there is an „authentication problem“ and you are not redirected to the login page.

The solution – 401 for API Calls

In the Startup.cs in method ConfigureServices provide a different logic for OnRedirectToLogin.

This is the simplest solution of all, by checking the request path for API calls. Of course you can also check the request header to see if it is an Ajax call.

By the way… this small piece of code took me quite a while to figure out. There are sooooo many outdated and wrong examples for this out there. I tried countless ones. They all compiled well, but the code never got executed.

NOT WORKING Examples:

All code examples that have a Provider property are outdated.

Summary

This article demonstrates how to change the status code from 302 to 401 for calls to specific controllers. In a future article I will demonstrate how to intercept 401 status codes in Ajax calls within AngularJS and redirect the user to a login page.

2 Antworten auf „302 Redirect VS 401 Unauthorized – ASP .NET 5 Identity“

  1. A motivating discussion is definitely worth comment.
    I think that you need to write more on this subject matter, it might not be a taboo
    subject but usually folks don’t talk about these topics. To the
    next! Cheers!!

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.