Response.redirect and server.transfer

Question

HI Friends What is response.redirect and server.transfer?

Satyapriya Nayak · Answer

Hi Akshay, Normal 0 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 Normal 0 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 location (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. Thanks

Prabhu Raja · Answer

Hi, 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)

Anuja Pawar · Answer

Hi Akshay, The Response.Redirect statement sends a command back to the browser to request the next page from the server. This extra round-trip is often inefficient and unnecessary, but this established standard works very well. By the time Page2 is requested, Page1 has been flushed from the server's memory and no information can be retrieved about it unless the developer explicitly saved the information using some technique like session, cookie, application, cache etc. The more efficient Server.Transfer method simply renders the next page to the browser without an extra round trip . Variables can stay in scope and Page2 can read properties directly from Page1 because it's still in memory. This technique would be ideal if it wasn't for the fact that the browser is never notified that the page has changed. Therefore, the address bar in the browser will still show "Page1.aspx" even though the Server.Transfer statement actually caused Page2.aspx to be rendered instead. This may occasionally be a good thing from a security perspective, it often causes problems related to the browser being out of touch with the server. Say, the user reloads the page, the browser will request Page1.aspx instead of the true page (Page2.aspx) that they were viewing. In most cases, Response.Redirect and Server.Transfer can be used interchangeably. But in some cases, efficiency or usability may be the deciding factor in choosing. For more detail refer http://aspdotnetfaq.com/Faq/what-is-the-difference-between-server-transfer-and-response-redirect-methods.aspx

Pravin Ghadge · Answer

Plz refer foll link. http://haacked.com/archive/2004/10/06/responseredirectverseservertransfer.aspx

Response.redirect and server.transfer

Answers (4)