Posted by Jonathan N. Little on 11/17/07 17:13

VK wrote:
> Accidentally I have read this thread and I noticed that the KB article
> I linked in "Active time for HTTP connection" thread may be giving
> another possible hint:
>
> http://support.microsoft.com/kb/813827
>
> "If you set the KeepAliveTimeout value to less than 60,000 (one
> minute), you may have problems communicating with Web servers that
> require persistent HTTP connections. For example, you may receive a
> "Page cannot be displayed" error message."
>
> It may be possible that some visitors have KeepAliveTimeout manually
> set to too short, or that for some requests the inactivity period goes
> beyond the default allowed 60,000ms
>
> I cannot reproduce your problem neither in IE6 nor IE7 so just
> guessing. If you have a machine stable reproducing the problem, then I
> would check one by one:
> 1) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
> \InternetSettings
> Try to set KeepAliveTimeout DWORD value to 180000 and add new key
> ServerInfoTimeout with DWORD value to 180000
>
> 2) Tools :: Internet Options :: Advanced :: HTTP 1.1 settings :: check
> on "Use HTTP 1.1 through proxy connections"
> (default is off)

If this is the case because the OP's "web app" requires such delays in
order process and transmit the site do you really expect visitors to
hack their default Windows' registry just to see the site? And we have
long-winded arguments whether or not the average user understands the
browser back button!

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[Back to original message]