Hi,
I've been having some problems that ultimately seem to be related to "Connection timeout" in IIS6. I'm building an ASP.NET application and some of the pages are doing long processing before they are displayed (reports, for example). If the processing takes more than 2 minutes, I can see an Timer_ConnectionIdle in the http.sys logs and also it seems that IE re-sends the request?!![[neutral]](/data/assets/smilies/neutral.gif "[neutral] [neutral]")
The request is a POST and if I increase the "Connection Timeout" it does not seem to reproduce.
Moreover, there is no entry in the w3svc logs confirming that the IE re-sent the POST, but the logging in my application confirms that (there is no bug in the code that could cause such hell).
Anyone ever heard about that? Is there a solution to prevent IE to re-send the POST? Or maybe some documentation, anything?
P.S.: Same situation with this guy (MS personnel vaguely responded)
I've been having some problems that ultimately seem to be related to "Connection timeout" in IIS6. I'm building an ASP.NET application and some of the pages are doing long processing before they are displayed (reports, for example). If the processing takes more than 2 minutes, I can see an Timer_ConnectionIdle in the http.sys logs and also it seems that IE re-sends the request?!
The request is a POST and if I increase the "Connection Timeout" it does not seem to reproduce.
Moreover, there is no entry in the w3svc logs confirming that the IE re-sent the POST, but the logging in my application confirms that (there is no bug in the code that could cause such hell).
Anyone ever heard about that? Is there a solution to prevent IE to re-send the POST? Or maybe some documentation, anything?
P.S.: Same situation with this guy (MS personnel vaguely responded)