redirect using HttpContextAccessor

Question

redirect using HttpContextAccessor

Michael P 20

Hi,

I am trying to redirect to my login page on a condition using IHttpContextAccessor. Here is my code :

if (condition)

{

_signInManager.SignOutAsync();

_httpContextAccessor.HttpContext.Response.Redirect("/Identity/Account/Login");

}

But the redirect doesn't happen and the code continues. Am I using this incorrectly or is there another way to do this?

Viorel 125.7K Reputation points

2025-12-12T13:20:25.9433333+00:00

For example, try to add a return statement after redirection.
Michael P 20 Reputation points

2025-12-12T14:09:55.5233333+00:00

I can't use a return statement as the action needs to return an IActionResult object.
AgaveJoe 30,411 Reputation points

2025-12-12T14:58:23.2366667+00:00

In ASP.NET Core (unlike the old Web Forms), Response.Redirect does not stop the execution of your code. It merely sets the "Location" header and the 302 status code on the response object.

If you do not return (or otherwise stop execution) immediately after calling it, the rest of your code will continue to run. This often results in the status code being overwritten back to 200 OK, or content being written to the body, which breaks the redirect.

To help us give you a more specific solution, could you clarify a few things?

Framework: What type of application are you building (Razor Pages, MVC, or Blazor)?

Context: Can you share the code block surrounding the redirect? (e.g., are you in a Controller, Middleware, or a Helper class?)

Answer accepted by question author

0 additional answers

Your answer

Viorel 125.7K Reputation points

2025-12-12T13:20:25.9433333+00:00

For example, try to add a return statement after redirection.
Michael P 20 Reputation points

2025-12-12T14:09:55.5233333+00:00

I can't use a return statement as the action needs to return an IActionResult object.
AgaveJoe 30,411 Reputation points

2025-12-12T14:58:23.2366667+00:00

In ASP.NET Core (unlike the old Web Forms), Response.Redirect does not stop the execution of your code. It merely sets the "Location" header and the 302 status code on the response object.

If you do not return (or otherwise stop execution) immediately after calling it, the rest of your code will continue to run. This often results in the status code being overwritten back to 200 OK, or content being written to the body, which breaks the redirect.

To help us give you a more specific solution, could you clarify a few things?

Framework: What type of application are you building (Razor Pages, MVC, or Blazor)?

Context: Can you share the code block surrounding the redirect? (e.g., are you in a Controller, Middleware, or a Helper class?)

Answer 1

Thank you for reaching out.

The issue happens because Response.Redirect() only writes a redirect header; it doesn’t stop the rest of the code from running in ASP.NET Core. The correct way is to return a redirect result, which satisfies the IActionResult requirement and properly ends the request.

Here’s the simple syntax you can use:

return`` Redirect("/Identity/Account/Login");

return`` RedirectToPage("Account/Login");

return`` LocalRedirect(returnUrl);

These methods are designed for controller actions and Razor Pages, so they work perfectly when your action returns IActionResult.

For more details, you can check the official Microsoft docs:

Please let us know if you require any further assistance, we’re happy to help.

If you found this information useful, kindly mark this as "Accept Answer".

Share via

redirect using HttpContextAccessor

0 additional answers

Your answer