Organizational Research By

Surprising Reserch Topic

internet explorer 8 timeout too quick on page posts

internet explorer 8 timeout too quick on page posts  using -',iis-7,internet-explorer-8,timeout'

We have an 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.

asked Sep 16, 2015 by santosh soni
0 votes

Related Hot Questions

2 Answers

0 votes

I think that the long term solution is not actually related to timeout configuration.

You're saying that only the first request takes a long time, and it takes > 10 seconds, so you should issue a warm-up request first after installing your application in a way that the first request load is never experienced by the end user.

answered Sep 16, 2015 by rajnipancholi
0 votes

A 10 second timeout might be a usability tool in disguise. 10 seconds is a pretty long time. Js capable browsers are > 99% now, why not push it off over Ajax and poll until the long work is done, then redirect to the next page? You could show the user more useful progress info in the meantime. If for some reason the next page itself is the source of the slow down and cannot be separated from its slow parts, you could finish by precaching the next page then redirecting.

answered Sep 16, 2015 by balvant maurya