Question

I’m coming across an odd issue when loading asp.net pages with IE9.

Basically, I’m working with a legacy system that is getting slowly updated and has some odd coding. The specific page loads, then has an iframe load a different page, basically a year 2000 version of async loading.

The problem is, that when the iframe page is loading (it needs to generate data so it may not return for close to half a minute or more), IE9 will not load any new pages from the current domain until the iframe page loads. So if a user visits this page and then decides they want to visit a different page instead, they have to wait for the iframe to finish loading before they can browse to a different page. Clicking the stop button first does nothing, the page still persists until the iframe loads.

This is a corporate web application so only IE is supported, but this problems does not appear to happen in Chrome (The page is badly broken otherwise, but the loading delay problem doesn’t exist)

Any thoughts?

Edit: I should add that Response.IsClientConnected always returns true unless the tab or browser is closed.

Answer 1

I found the solution.

It turns out that IIS keeps the session for a user thread-safe, so only one page can access it at a time. When the page inside the iframe was processing, it locked the Session thus making any other pages wait until it finished, hence the delay.