Understanding ASP.NET Response.Redirect

Posted by: Rob Howards Blog, on 24 Oct 2007 | View original | Bookmarked: 0 time(s)

ASP.NET has a wonderful carry over from Classic ASP that many developer still use: Response.Redirect(string url); When ASP.NET encounters a Redirect() request it will internally throw a thread abort exception and immediately send headers back to the client (typically a browser) to go to another URL. There are a couple of things to be aware about when you use Response.Redirect(): 1. Internally a ThreadAbort exception is thrown. This is normal and if you monitor your CLR exceptions and use Response.Redirect()...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 2922 | Hits: 443

Similar Posts

  • ASP.NET disk-based caching more
  • Redirects, 301, 302 and IIS SEO Toolkit more
  • Don’t use Response.End() with OutputCache more
  • IIS 7 Error Pages taking over 500 Errors more
  • Brokered authentication for REST active clients with SAML more
  • SharePoint Development Best Practices (Summary) more
  • The DefaultButton Property - News To Me! more
  • DataSprings Dynamic Forms Completion Events more
  • RedirectButton - Redirect Users With the Click of a Button more
  • EOAST #4 Evolution of a software thingy Part 4 more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD