Bug 7915 - ASP.NET returning 302 instead of 401 (Unauthorized)
Summary: ASP.NET returning 302 instead of 401 (Unauthorized)
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-10-21 10:01 UTC by marxin.liska
Modified: 2012-10-21 10:01 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 7915 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description marxin.liska 2012-10-21 10:01:43 UTC
   we use MVC 4 for our Web application. We hit following problem in our controller:

public ActionResult Detail(LoginViewModel loginVM)
  if (!authenticator.LogIn(loginVM.Username, loginVM.Password))

  return View("Detail", loginVM);

We want to return 401 status code, but is overwritten by 302, let's see following article: http://blog.nvise.com/?p=26.

Is it bug or ASP.NET feature?