UpdatePanel Async Postsback slow in IE…Part 2

I have a small update to the slow UpdatePanel Async Postback issue.

Microsoft has updated their temporary fix that they provided to me last week:  http://support.microsoft.com/kb/2000262.

I am still working with them on this script as we found some more problems with it today.  I recommend not using it right now.

Permanent Redirect with HTTP 301

How to properly do a permanent redirect with a HTTP 301.

ASP.NET 4.0 gives us this:

ASP.NET 4.0 adds a new RedirectPermanent helper method that makes it easy to issue HTTP 301 Moved Permanently responses, as in the following example:

RedirectPermanent("/newpath/foroldcontent.aspx");

ASP.NET 4.0 Auto-Start Applications, I can’t wait…

If you have ever dealt with a memory intensive ASP.NET web application you know how valuable this new Auto-Start feature will be.

Some Web applications need to load large amounts of data or perform expensive initialization processing before serving the first request. In earlier versions of ASP.NET, for these situations you had to devise custom approaches to “wake up” an ASP.NET application and then run initialization code during the Application_Load method in the Global.asax file.

A new scalability feature named auto-start that directly addresses this scenario is available when ASP.NET 4.0 runs on IIS 7.5 on Windows Server 2008 R2. The auto-start feature provides a controlled approach for starting up an application pool, initializing an ASP.NET application, and then accepting HTTP requests.

UpdatePanel Async Postsback slow in IE….what!?

How can it be that this problem only occurs in IE.  It is their technology on their platform!

When using Internet Explorer to browse a page that contains an UpdatePanel, there is a delay (often anywhere between 10 seconds and 45 seconds or more) after clicking a page element that initiates an async postback. The delay is not experienced when using browsers other than Internet Explorer.

FYI,  FireFox’s performance is superior on the same code base in my experiences so far.  I have opened up a case with Microsoft, so we will see what the IE team has to say.  More to come…

http://support.microsoft.com/kb/2000262