ThreadAbortException occurs if you use Response.End, Response.Redirect, or Server.Transfer

This article helps you resolve the ThreadAbortException error that occurs if you use Response.End, Response.Redirect, or Server.Transfer.

Original product version:   ASP.NET on .NET Framework 4.6.2 or later, ASP.NET on .NET Framework 3.5 Service Pack 1
Original KB number:   312629

Symptoms

If you use the Response.End, Response.Redirect, or Server.Transfer method, a ThreadAbortException exception occurs. You can use a try-catch statement to catch this exception.

Cause

The Response.End method ends the page execution and shifts the execution to the Application_EndRequest event in the application's event pipeline. The line of code that follows Response.End isn't executed.

This problem occurs in the Response.Redirect and Server.Transfer methods because both methods call Response.End internally.

Resolution

To work around this problem, use one of the following methods:

• For Response.End , call the HttpContext.Current.ApplicationInstance.CompleteRequest method instead of Response.End to bypass the code execution to the Application_EndRequest event.

• For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example:

  Response.Redirect ("nextpage.aspx", false);
  

  If you use this workaround, the code that follows Response.Redirect is executed.

• For Server.Transfer, use the Server.Execute method instead.

Although ASP.NET handles this exception, you can use the try-catch statement to catch this exception. For example:

try
{
    Response.Redirect("nextpage.aspx");
}
catch (Exception ex)
{
    Response.Write (ex.Message);
}

Add a breakpoint on the Response.Write line, and notice that this breakpoint is hit. When you examine the exception, notice that the ThreadAbortException exception occurs.