blocks|key|8127|text|这是设计好的。此KB+article描述行为(也适用于Request.End()和Server.Transfer()方法)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|8128|对于Response.Redirect()，存在重载：|8129|Response.Redirect(String+url,+bool+endResponse)|code-block|syntax|javascript|8130|如果传递endResponse=false，，则不会抛出异常(但运行时将继续处理当前请求)。|BOLD|8131|如果为endResponse=true+(或者如果使用不带bool参数的重载)，则会抛出异常，并且当前请求将立即终止。|8132|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/312629^0|R|D|15|H|8|A|0|0|2|J|0|0|4|H|0|3|G|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1B|8|@$9|1C|A|1D|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1E|8|@$9|1F|A|1G|B|O]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]]]

This is by design. This <a href="http://support.microsoft.com/kb/312629" rel="noreferrer">KB article</a> describes the behavior (also for the <code>Request.End()</code> and <code>Server.Transfer()</code> methods).

For <code>Response.Redirect()</code> there exists an overload:

<pre><code>Response.Redirect(String url, bool endResponse)
</code></pre>

If you pass endResponse=false, then the exception is not thrown (but the runtime will continue processing the current request).

If endResponse=true (or if you use the overload without the bool argument), the exception is thrown and the current request will immediately be terminated.

blocks|key|1571662|text|这很正常。Server.Transfer()也会抛出同样的异常。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1571663|这是因为在内部，这两个方法都调用Response.End()，它会立即中止当前的请求处理。Rick+Strahl有一个pretty+good+blog+post，它分析了为什么您几乎无法避免这些异常。|1571664|entityMap|0|LINK|mutability|MUTABLE|url|http://www.west-wind.com/WebLog/posts/368975.aspx^0|5|H|0|G|E|1N|L|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

This is normal. <code>Server.Transfer()</code> also throws the same exception.

This is because internally, both methods call <code>Response.End()</code>, which aborts the current request processing immediately. Rick Strahl has a <a href="http://www.west-wind.com/WebLog/posts/368975.aspx" rel="nofollow noreferrer">pretty good blog post</a> that analyzes why there is pretty much nothing you can do to avoid these exceptions.

blocks|key|8245|text|Response.Redirect在内部调用Response.End，因此它会抛出异常，请改用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8246|Response.Redirect(url,+false);|code-block|syntax|javascript|8247|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Response.Redirect calls Response.End internally, so it throws the exception, use instead : 

<pre><code>Response.Redirect(url, false);
</code></pre>

blocks|key|270009|text|这是正常的，因为这是注定要发生的事情。基本上，当响应被设置为重定向时，ASP.NET期望您完全完成请求。它会中止线程，以防止发生任何其他处理(基本上它会为您调用Response.End，然后抛出异常)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|270010|在我看来，这有点滥用异常，但这就是它的工作方式。如果您愿意，可以使用具有第二个参数(并传递false)的重载来防止这种情况发生-但如果是这样的话，请确保没有其他内容尝试写入响应！|270011|entityMap^0|28|C|0|19|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

It's normal in that it's what's meant to happen. Basically when the response has been set to a redirection, ASP.NET expects that you're completely done with the request. It aborts the thread as a way of preventing any other processing from occurring (basically it calls <code>Response.End</code> for you, and that throws the exception).

It seems to me that it's a bit of an abuse of exceptions, but that's the way it works. You can use the overload which has a second parameter (and pass <code>false</code>) to prevent this from happening if you want to - but if so, make sure that nothing else then tries to write to the response!

blocks|key|1569235|text|我认为您需要遵循这篇知识库文章中的说明。Response.Redirect调用Response.End()，除非您使用了专门为避免此行为而设置的重载。一旦响应结束，就不能再进行进一步的操作，因此TA+exc。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1569236|http://support.microsoft.com/kb/312629|offset|length|1569237|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|12|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I believe you need to follow the instrucitons in this KB article. Response.Redirect calls Response.End(), unless you used the overload specifically made to avoid this behavior. Once the response has been ended, no further operations can happen hence the TA exc. 

<a href="http://support.microsoft.com/kb/312629" rel="nofollow noreferrer">http://support.microsoft.com/kb/312629</a>

blocks|key|1413029|text|该行为被设计为支持旧的asp。这是来自微软的链接，描述了你正在经历的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413030|http://support.microsoft.com/default.aspx?scid=kb;EN-US;312629|offset|length|1413031|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1Q|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

The behavior is by design to support old asp. Here is the link from MS describing what you are experiencing. 

<a href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;312629" rel="nofollow noreferrer">http://support.microsoft.com/default.aspx?scid=kb;EN-US;312629</a>

blocks|key|1569347|text|调用Redirect()的重载也会导致对Response.End()的调用，这会抛出一个ThreadAbort异常，以确保页面/UC中的重定向之后没有其他代码运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1569348|您不应该捕获此异常..您应该在代码中忽略它，或者使用Redirect()的重载，它接受一个布尔值，该布尔值指示在重定向之后是否继续处理请求。|1569349|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Calling the overload of Redirect() that just takes a URL also results in a call to Response.End() - which throws a ThreadAbort exception to ensure that no other code after the redirect in your page/UC is run.

You shouldn't catch this exception .. you should either ignore it in your code or use the overload of Redirect() which takes a boolean that indicates whether to continue processing the request after the redirect.

blocks|key|8343|text|嗯。我在那之后编写了一个出口潜水艇，但我知道它不能到达。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8344|我想，如果你想这样做，你可以吃了异常，在后面继续更多的东西，但我不推荐这样做。|8345|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Yeah. I code an exit sub after those but I know it's not reached.

I suppose if you wanted to you could eat the exception and carry on more stuff afterwords but I wouldn't recommend it.

blocks|key|270141|text|这里已经有一堆合理的答案了。不过，还有一点值得注意。Thread+Abort异常是一种罕见的异常，您可以捕获它并针对它进行编码，但不能禁止它。无论您执行什么操作，它都会在任何try/catch/finally块的末尾自动重新引发。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270142|如果你决定接受这个异常，你应该确保你的健康监控允许它，并且不会把它报告为一个问题，这样你就不会被困在一群非技术经理面前，他们试图解释为什么你的网站抛出了这么多线程异常。(我让一位经理确信，所有这些线程中止都会留下一个烂摊子，这当然与线程中止的目的完全相反。)|270143|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Already a bunch of reasonable answers here. One other point worth noting though. The Thread Abort Exception is one of those rare exceptions that you can catch and code against, but you can't suppress. It gets automatically re-raised at the end of any try/catch/finally block regardless of what you do.

And if you decide to live with this exception, you should ensure that your health monitoring allows for this and doesn't report it as an issue, so you don't get stuck in front of a bunch of non-technical managers trying to explain why your website is throwing so many Thread Abort Exceptions. (I had a manager convinced that all these thread abortions were leaving a mess behind which of course was the complete opposite to the intention of the thread abort.)

I am learning ASP.NET and was looking at QueryStrings.

One of the examples I was looking at hooks a button up to a redirect call:

<pre><code> protected void btnSubmit_Click(object sender, EventArgs e)
 {
 try
 {
 //throws ThreadAbortException: "Thread was being aborted"
 Response.Redirect("Form2.aspx");
 }
 catch (Exception Ex)
 {
 System.Diagnostics.Debug.WriteLine(Ex.Message);
 }
 }
</code></pre>

Why does it throw a ThreadAbortException here? Is that normal? Should I do something about this? Exceptions are generally not a good thing, so I was alarmed when I saw this.

Why do I get a thrown exception when I run Response.Redirect()?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在学习ASP.NET，并且正在研究QueryStrings。我看到的一个例子是将一个按钮挂接到一个重定向调用：    protected void btnSubmit_Click(object sender, EventArgs e)    {        try        {            //throws ThreadAbortException: "Thread was b

问为什么在运行Response.Redirect()时会抛出异常？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么在运行Response.Redirect()时会抛出异常？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么在运行Response.Redirect()时会抛出异常？
EN