What is a valid use for Response.Redirect ("SomeURL", false)?

In ASP.NET, I often use Response.Redirect to redirect the end user to another page on my system. I always set the second parameter to true to immediately complete the response.

In my life, I cannot think of why anyone ever set this parameter to false. What is the point of continuing to create the page when the end-user’s browser is simply redirected to another page right away?

+5
source share
4 answers

Response.Redirectdoes not mean that the server has run out of the Page-lifecycle , it just sends it to the client .

, , ?

HttpServerUtility.Transfer , , .

+6
Response.Redirect(..., true);

,

Response.Redirect(..., false);

, , , - -

+6

. , - , . , , . , .

+1
source

Response.Rediect("any page like Default.aspx");

When control reaches this statement, our page will go to the page indicated in parentheses. The page can be .aspx, .asp.htm, etc.

-1
source

All Articles