Thread aborted using Response.Redirect in ASP.Net

by demtron on Monday, February 02, 2009 08:13 AM

I added a Response.Redirect to a .Net Web page and began receiving a "Thread was being aborted" error on a line of code that executed Response.Redirect.  Without really considering it, this error made sense based on the place where I added the code.

Response.Redirect will call Response.End by design.  However, this will also raise a ThreadAbortException.  In my case, it was because the redirect line was within a try...catch block.  I found two ways to handle this:

  1. Change Response.Redirect(<URL>) to Response.Redirect(<URL>, false)
  2. Move the line to outside the try...catch block
I ended up using method #2, but both options worked for me.

Detect AJAX postback in Global.asax

by demtron on Friday, January 16, 2009 08:19 AM

I was recently working on a page hit logging scenario that, for reasons having to do with URL rewriting, needed to have the logging code executed in the Application.BeginRequest event of Global.ajax.  The application relies heavily on ASP.Net Ajax, and I needed a was to ferret out the AJAX requests and not log them.  Ordinarily, in the page lifecycle, this would be accomplished by using Page.IsAsync.  In this case, I needed to perform the logging prior to the page code being invoked.

To determine the whether the request was generated by AJAX, I used the following code:


Request.Headers("X-MicrosoftAjax") = "Delta=true"


Request.Headers["X-MicrosoftAjax"] = "Delta=true";

Hope that helps someone out there who has struggled to find an easy answer.

Powered by BlogEngine.NET
Theme by Mads Kristensen · Adapted by Demtron

Bookmark and Share


<<  February 2023  >>

View posts in large calendar
Log in

Milwaukee SEO Company

Milwaukee Access Programmer/Developer

Milwaukee Website Designer and Developer

Marketing / SEO

Blog Directory
blogarama - the blog directory
Milwaukee area SEO, SEM, ASP.Net