0

I am working on a legacy system where an intermittent problem keeps happening at what seems to be times where there is a lot of load on the network. I am using IE6 to access a webpage generated by a CGI-script (the actual HTML generation takes quite a bit of time as well), and the problem manifests itself by cutting the HTTP response short, so all HTML code does not get sent to the browser which renders an incomplete page. I initially thought that this might have something to do with timeouts on the server side, but all the timeouts seem to be quite normal and I cannot see any errors at relevant times in the HTTPERR log.

However, looking at Wireshark logs, it seems like the server sends part of the data, and then client sends a "FIN, ACK" to the server to begin to close the TCP connection some seconds before the server starts to send the rest of the data, which the client then does not want to handle because it thinks that the connection is no longer active.

Does anybody have any tips how I can find out why the IE6 would prematurely cancel a connection?

Improve this question
2
  • 1
    Speeding up the ancient web app isn't an option? This is 2013, after all. IE6 is a walking corpse, and that web app is probably close to the same.
    – Michael Hampton
    May 8, 2013 at 16:14
  • @MichaelHampton +1 for calling IE6 a walking corpse. lol
    – Reactgular
    May 9, 2013 at 14:35

1 Answer 1

Reset to default
2

You could try adjusting the default timeout value of IE. See this article for more information.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .