What is the difference between Server.Transfer and
Response.Redirect?
- 4 Answers
- 4731 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / kishore maddineni
1) Response.redirect() is used to navigate between with in
one application, where as server.transfer() is used to
navigate between applications.
2)in Response.redirect() URL is updated, where as in
server.transfer() URL is not updated.
3)in Response.redirect() occured two round trips to the
server, where as in server.transfer() occured only only
round trip.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / kinjal
server.transfer is processing direct one page to the another page without round trip to back to the client browser.
response.redirect is processing round trip from one page to another page and back to the client browser.
server.transfer is better than response.redirect.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / gitam singh
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.
Response.Dedirect() :client knows the physical location (page name and query string as well). Context.Items loses the persistence when navigate 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.
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / versha
in case of server.transfer it transfer from server to server
but in case of response.redirect it transfer from page to
another page in one site
| Is This Answer Correct ? | 0 Yes | 2 No |
How is threading done in .net?
What's wrong with a line like this? Datetime.parse(mystring);
What does SCM do?
What is concurrency? How will you avoid concurrency when dealing with dataset?
What is new in .net core?
What are server controls?
What are an object and a class?
When should I use .net core?
What are the authentication methods in .net?
What is the benefit of .net core?
How do you turn off cookies for one page in your site?
What is iis? Have you used it?
Dot Net Framework 
