views:

782

answers:

5

We have an asp.net site running, which has been working fine for some time, but recently I have been experiencing some issues with IE8.

On posting some pages - mainly on our development server, although on staging too - we get an occasional "Internet Explore cannot display the webpage" error along with the button asking to diagnose connection problems. IE only seems to wait 10 seconds before timing out. I know that the page itself may take longer to load the first time (on dev and staging). So press F5 and everything then works fine.

Is there anything that should be done in the aspx page to tell IE to wait a bit longer?

I thought I had read that the default timeout supposed to be 90 seconds or something for browsers.

A bit more info:

It mostly happens on a POSTing a signup page, but that is just because I test that page and it starts the IIS App, makes the first connection to SQL and pre-caches some information. That first time the page can take 10-15 seconds to come back. IE8 times out after 10 seconds as it has had nothing back.

This happens on a dev W7x64 machine with 8GB RAM, as well as on a staging server WIN2008.

Having googled around a bit, some people are seeing the same problem, but no conclusive pointers to the problem or a solution.

It isn't a connection problem; everything works fine in Firefox, Chrome and even IE7; I have tried with add-ons disabled and resetting IE settings, still happens.

Ideas welcome.

A: 

Check your Application pool Advanced settings in IIS. It may be lower than is normal. Maybe the Ping period? Mine is 30secs

BritishDeveloper
I have the same, default of 30s.
cdm9002
actually since this only happens in IE i doubt it will be an IIS issue. Long shot: do you have an incredibly short cookie expiry?
BritishDeveloper
A: 

I think you may have to check this link out :

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

Braveyard
That says 5 mins. I am seeing 10 secs timeout.
cdm9002
A: 

I am having the exact same problem when posting to a servlet that can take up to 30 seconds to return. The page times out after 10 seconds even though the servlet continues to process. If the servlet doesn't return within 10 seconds, the user never gets the response. It happens on one computer with XP/IE8, and it does NOT happen on a different computer with XP/IE8. It does not happen in Firefox or IE7. Did you ever find any solutions?

a tester
I have found a solution, a setting changed by some installers. I put details in comments on my original question. Hope it helps you.
cdm9002
A: 

yep, I discovered the exact same thing after I wrote this yesterday. I was hoping for a solution that doesn't involve telling users to edit their registry settings. Oh well. Thanks for posting back.

a tester
A: 

This also happened to me when I installed the latest version of WebRoot's SpySweeper (on 8/3/2010). It changed the ReceiveTimeout to 10 seconds and thoroughly hosed some of our more processing-intensive pages. I, too, had to use the registry hack.

This is pure, unmitigated evil.

David