Click here to Skip to main content
15,881,600 members
Articles / Web Development / ASP.NET
Article

Using Response.Redirect and Response.End in Try...Catch block

Rate me:
Please Sign up or sign in to vote.
0.00/5 (No votes)
11 Oct 2013CPOL 15.1K   1  
Using Response.Redirect and Response.End in Try...Catch blockIn ASP.NET if you are using Response.End - Used for terminating page execution or

This articles was originally at wiki.asp.net but has now been given a new home on CodeProject. Editing rights for this article has been set at Bronze or above, so please go in and edit and update this article to keep it fresh and relevant.

Using Response.Redirect and Response.End in Try...Catch block

In ASP.NET if you are using Response.End - Used for terminating page execution or Response.Redirect - used for redirecting page to some other page, and you are including these statements in TRY... CATCH block here is what you need to remember.

Problem: 

When Response.Redirect or Response.End is written in TRY block, code in catch block is executed.

Reason:

ASP.NET executes these 2 methods on Response object by throwing ThreadAbort Exception. When written in simple Try...Catch block this results in Catch block catching this exception and processing code written in catch block. This causes unwanted code execution e.g. error logging or genric error display code which is generally written in Catch block.

Solution:

You need to handle ThreadAbort exception separately and do nothing if it is thrown. Refer following code patch:

try
{
                 // Your actual code

                Response.End();
}

catch
(ThreadAbortException exc)
{
                 // This should be first catch block i.e. before generic Exception
                 // This Catch block is to absorb exception thrown by Response.End
}
catch (Exception exc)
{
                // Write actual error handling code here
}

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
United States United States
The ASP.NET Wiki was started by Scott Hanselman in February of 2008. The idea is that folks spend a lot of time trolling the blogs, googlinglive-searching for answers to common "How To" questions. There's piles of fantastic community-created and MSFT-created content out there, but if it's not found by a search engine and the right combination of keywords, it's often lost.

The ASP.NET Wiki articles moved to CodeProject in October 2013 and will live on, loved, protected and updated by the community.
This is a Collaborative Group

754 members

Comments and Discussions

 
-- There are no messages in this forum --