Why Response.Redirect always throws an exception internally which gets resolved automatically by the framework

Question

2.00/5 (1 vote)

See more:

I just encountered “System.Threading.ThreadAbortException” exception if I write Response.Redirect in a try block. See below the code I have written.

C#

protected void btnVisitSecondPage_Click(object sender, EventArgs e)

Response.Redirect("frmSecondPage.aspx");
}
catch (Exception ex) { } 
}

Above code is working fine but if I debug it, I can see Response.Redirect throws “System.Threading.ThreadAbortException” exception and gets resolved by the framewrok autonmatically.

Most strange part is that if I remove the try block then it also works fine without throwing an exception .

See below the code

C#

protected void btnVisitSecondPage_Click(object sender, EventArgs e)Response.Redirect("frmSecondPage.aspx");

Can any one please give me the explanation ?

Posted 20-Nov-09 17:14pm

Bibhas Paul

Updated 12-Feb-21 1:09am

RaisKazi

v10

Add a Solution

6 solutions

Solution 1

I have just tried a new web application with 2 pages,

Page1 had a button with a response.redirect to page2

Page2 had a button with a response.redirect within a try block to page1.

It works fine without any issue.

Posted 20-Nov-09 20:13pm

DaveAuld

Updated 20-Nov-09 20:14pm

v2

Solution 4

Response.Redirect always throws a excpetion.
Best thing to do is catch the type of exception you want.

Posted 5-Dec-13 4:42am

Forbiddenx

Comments

CHill60 5-Dec-13 10:43am

You do realise that this question is 4 years old?

SoMad 6-Dec-13 3:22am

That has to be some kind of record :). Maybe someone should tell Dave that he has a message waiting in Solution 2 :).

Soren Madsen

phil.o 5-Dec-13 10:56am

Nice post-digging!

Solution 2

Hi Daveauld, Thanks for your response. Yes, this is true. Even this is working for me also. But if you set a debug point and press F11 key to run your example. Then you can see Response.Redirect is throwing an execption which is getting resolved automatically and at last Response.Redirect is working. Looking forward from hearing to you.

Posted 22-Nov-09 1:00am

Bibhas Paul

Solution 5

Response.Redirect(url, false);
Context.ApplicationInstance.CompleteRequest();

a href="http://stackoverflow.com/questions/2777105/why-response-redirect-causes-system-threading-threadabortexception

Posted 18-Aug-16 20:33pm

sinaj75

Solution 6

Response.Redirect("Home.aspx", false);
Context.ApplicationInstance.CompleteRequest();

Posted 12-Feb-21 1:09am

Member 13979303

Comments

CHill60 15-Feb-21 10:40am

Copy of Solution 5. Don't copy previous posts

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

*dan!sh* · Accepted Answer · 2009-11-22T02:19:00

Solution 3

Read this article: http://support.microsoft.com/kb/312629/EN-US/

I hope it explains your problem.

Posted 22-Nov-09 2:19am

dan!sh