Response.Redirect
simply sends a message (HTTP 302) down to the browser.
Server.Transfer
happens without the browser knowing anything, the browser request a page, but the server returns the content of another.
More Related Contents:
- Server.Transfer Vs. Response.Redirect
- Redirect to a page with endResponse to true VS CompleteRequest and security thread
- ASP.NET Push Redirect on Session Timeout
- 404 Redirecting for non aspx pages
- Default redirect for Error 404
- Where does Console.WriteLine go in ASP.NET?
- How to create Custom Data Annotation Validators
- Stored procedure slow when called from web, fast from Management Studio
- Routing for custom ASP.NET MVC 404 Error page
- .Net picking wrong referenced assembly version
- ASP.NET authentication login and logout with browser back button
- MemoryCache Empty : Returns null after being set
- How does IsMobileDevice work?
- How do you avoid XSS vulnerabilities in ASP.Net (MVC)?
- How to allow download of .json file with ASP.NET
- How can I use the button tag with ASP.NET?
- ASP.NET Stress Testing
- PhantomJS as web job in Azure
- file download by calling .ashx page
- Entity Framework 4 – Update database schema from model. Without wiping the table data
- How to deliver big files in ASP.NET Response?
- ASP.NET Web Site or ASP.NET Web Application?
- What is the difference between ‘dependencies’ and ‘frameworkAssemblies’ in project.json?
- ASP.Net Text with LineBreak from Multi-Line-TextBox to save in a database
- web.config and app.config confusion
- Using a Razor @functions in several webpages (.cshtml files)
- Requests hanging on Session module on IIS 7.5
- Proper way to use JQuery when using MasterPages in ASP.NET?
- What is a Generic Handler in asp.net and its use?
- How does Html.Raw MVC helper work?