Home Library Learn Downloads Support Community
Sign in | United States - English | |
10 out of 39 rated this helpful - Rate this topic

HttpResponse.Redirect Method (String, Boolean)

.NET Framework 2.0

Redirects a client to a new URL. Specifies the new URL and whether execution of the current page should terminate.

Namespace: System.Web
Assembly: System.Web (in system.web.dll)

C#
C++
VB
Copy 
public void Redirect (
	string url,
	bool endResponse
)
J#
Copy 
public void Redirect (
	String url, 
	boolean endResponse
)
JScript
Copy 
public function Redirect (
	url : String, 
	endResponse : boolean
)

Parameters

url

The target location.

endResponse

Indicates whether execution of the current page should terminate.

Exception type Condition

HttpException

A redirection is attempted after the HTTP headers have been sent.

An absolute URL (for example, http://www.contoso.com/default.aspx) or a relative URL (for example, default.aspx) can be specified for the target location but some browsers may reject a relative URL.

Redirect calls End which raises a ThreadAbortException exception upon completion.

The following code example uses the IsClientConnected property to check whether the client requesting the page remains connected to the server. If IsClientConnected is true, the code calls the Redirect method, and the client will view another page. If IsClientConnected is false, the code calls the End method and all page processing is terminated.

C#
VB
Copy 
<%@ Page Language="C#" %>
<script runat="server">

    private void Page_Load(object sender, EventArgs e)
    {
        // Check whether the browser remains
        // connected to the server.
        if (Response.IsClientConnected)
        {
            // If still connected, redirect
            // to another page. 
            Response.Redirect("Page2CS.aspx", false);
        }
        else
        {
            // If the browser is not connected
            // stop all response processing.
            Response.End();
        }
    }

</script>
<html>
<head>
</head>
<body>
    <form runat="server">
    </form>
</body>
</html>

Windows 98, Windows 2000 SP4, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.

.NET Framework

Supported in: 2.0, 1.1, 1.0
Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Even w/true, it doesn't _always_ end the response immediately!
Careful!! If you pass true, Response.Redirect() calls Response.End(), however there are certain circumstances where Response.End() does not raise the ThreadAbortException and instead sets a couple of flags and returns. One such situation is when you're in Global.asax, but it would occur more generically in any execution step that was not cancellable. I'll add details on Response.End(), but in a page you'd be fine, but in Global.asax processing will continue even if you pass true as the second parm.
History
When Does redirect happen?
Does the redirect information get sent to the client when the response.redirect is executed or when the page finishes?
History
Losing session information about a redirect

If you do a Response.Redirect which results in Response.End() being called (either passing true as the 2nd paramter, or not passing a 2nd parameter at all), you will lose session data if it's the first time you write session information for the user. For example, after a login, you might set do:

Session["userId"] = userId;

Response.Redirect("admin.aspx");

The solution is to call Response.Redirect("admin.aspx", false);

 

You will only lose session data if the session does not yet exist when you do the redirect. What doesn't get set here is not the session data in itself, it's the cookie that identifies the session.

 

Betrand LeRoy explains this in greater detail:

http://weblogs.asp.net/bleroy/archive/2004/08/03/207486.aspx 

History
ThreadAbortException not raised when endResponse is false
Response.End() is not called when endResponse is false. The page will fully process and the response header will be sent out.
History