response.Transfer And response.Redirect

The key differences between the two methods are:

1.  Response.Redirect causes a new request to be initiated, while Server.Transfer does not.
2.  Response.Redirect changes the URL in the client's browser, while Server.Transfer does not.
3.  Response.Redirect is useful when you want to redirect the user to a different website or when you want to pass information to the new page using query string parameters. Server.Transfer is useful when you want to transfer control to another page on the same server without changing the URL.

In general, Response.Redirect is more commonly used than Server.Transfer.

Hi Deepak,

Response.Redirect sends a response to the client browser instructing it to request the second page. This requires a round-trip to the client, and the client initiates the Request for the second page. Server.Transfer transfers the process to the second page without making a round-trip to the client. It also transfers the HttpContext to the second page, enabling the second page access to all the values in the HttpContext of the first page


Server.Transfer: client is shown as it is on the requesting page only, but the all the content is of the requested page. Data can be persist across the pages using Context.Item collection, which is one of the best way to transfer data from one page to another keeping the page state alive.



Server.Transfer transfers execution directly to another page. Response.Redirect sends a response to the client and directs the client (the browser) to load the new page (it causes a roundtrip). If you don't need to execute code on the client, Transfer is more efficient.


Thanks