Response.Redirect and Server.Transfer

Question

Difference between Repect.Redirect and Server.Transfer

Purushottam Rathore · Answer

Response.Redirect will redirect the page like client has requested to redirect the page. When you use the Server.Transfer, the page will be redirected without the client interaction. In the Server.Transfer, you can pass the form values from one page to another without using the query string. If you use Server.Transfer, you can't transfer the control to another server. Response.Redirect: Allows redirection to any url Client will be able to see new url Paramaters can be passed to new pages Paramaters are visisble to client users Server.Transfer Can only be used within application Allows values to be passed between pages Client users are unaware of new page New page url is oblivious to users. Context.Items to hold and pass information between pages Lower cost of usage on server handling http requests (however all page contents are held on Context.Handler)

Niradhip Chakraborty · Answer

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 accros 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. Response.Dedirect() :client know the physical loation (page name and query string as well). Context.Items loses the persisitance when nevigate to destination page. In earlier versions of IIS, if we wanted to send a user to a new Web page, the only option we had was Response.Redirect. While this method does accomplish our goal, it has several important drawbacks. The biggest problem is that this method causes each page to be treated as a separate transaction. Besides making it difficult to maintain your transactional integrity, Response.Redirect introduces some additional headaches. First, it prevents good encapsulation of code. Second, you lose access to all of the properties in the Request object. Sure, there are workarounds, but they’re difficult. Finally, Response.Redirect necessitates a round trip to the client, which, on high-volume sites, causes scalability problems. As you might suspect, Server.Transfer fixes all of these problems. It does this by performing the transfer on the server without requiring a roundtrip to the client. Examples: Server.Transfer Server.Transfer("Webform2.aspx") Response.Redirect Response.redirect("Webform2.aspx")

Gaurav Tomar · Answer

Hi buddy, By using Response.Redirect , you simply redirect user to another page. Server.Transfer also sends user to another page but "transfer" process can work on only those sites running on the server, you can't use Server.Transfer to send the user to an external site. Only Response.Redirect can do that.