好久没上优快云今天早上碰到点小问题

最新推荐文章于 2025-12-25 07:50:54 发布

原创最新推荐文章于 2025-12-25 07:50:54 发布 · 611 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#application #methods #exception #string #url

学习心得专栏收录该内容

12 篇文章

订阅专栏

本文介绍了在使用Response.End, Response.Redirect或Server.Transfer方法时遇到ThreadAbortException异常的原因及解决方案。建议使用HttpContext.Current.ApplicationInstance.CompleteRequest替代Response.End，或通过Response.Redirect(url, false)的方式避免内部调用Response.End。

在网上搜了下找到答案了

ThreadAbortException Occurs If You Use Response.End, Response.Redirect, or Server.Transfer

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 is not 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.