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 - mainl
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.
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.
Check your Application pool Advanced settings in IIS. It may be lower than is normal. Maybe the Ping period? Mine is 30secs
Try this out
<httpRuntime executionTimeout="15"/> under system.web in the web.config