Response.redirect throws thread exception

Question

0.00/5 (No votes)

See more:

Response Redirect Throw Exception as Thread Exception as

Unable to Evaluate Expression because the code is optimized or a native frame is on top of the call stack

What I have tried:

I have tried Response.Redirect("/google.com", false). Which is not executes since Endresponse is false it will not call redirect.

Posted 20-Jan-19 23:53pm

Member 12640353

Updated 21-Jan-19 2:13am

Add a Solution

Comments

ZurdoDev 21-Jan-19 7:17am

As I recall, you can ignore that error. It's because you are ending the current thread by going somewhere else. Just google the error number and you'll see that you can catch that error and ignore it.

1 solution

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)

MadMyche · Answer 1 · 2019-01-21T02:13:00

Fought this a few years ago, was getting a ThreadAbort Exception.

Option 1 is to wrap it in a Try...Catch block and ignore it. Generally I do not catch exceptions and ignore, but this case is special

C#

try { Response.Redirect(url); }
catch (ThreadAbortException) {/* no real action performed */}

Option 2 is to allow the thread to continue executing after the redirect, best to do the redirect as the last part of a process. Otherwise there could be performance impacts.

C#

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