This week we faced strange issue [Oh yes, Issues are always strange, that’s why we know them as an issue! :-)].
Basically we were running a long running operation on server and in between our browser displayed “Internet Explorer cannot display the webpage” page. (Needless to say, we are using Internet Explorer) We checked at our server-side (logs, sql connection, web server etc.) and everything was perfect! We were clueless whether our server operation got completed or not.
If you are also facing this same issue, then keep reading we have a solution for you!
Okay, so we were clueless what to do? Then suddenly it stroked in my mind. As IE shown this error page, why not try the same process with Firefox? [So long back faced similar issue and tried with FF and it worked. But at that time never researched why it worked!]
And you guess what? It worked for us. i.e. the same process got completed without changing anything on server-side code!
Okay, so we were happy as our task got completed. But we were not sure why it worked. [And my colleague Muktesh asked me a question, why it worked?].
Really good question! Then I started my research and found something interesting to share with all of you! Really interesting to read here you go:
Following Stackoverflow thread has some good points on this:
By design, Internet Explorer imposes a time-out limit for the server to return data. The time-out limit is five minutes for versions 4.0 and 4.01 and is 60 minutes for versions 5.x, 6, and 7. As a result, Internet Explorer does not wait endlessly for the server to come back with data when the server has a problem.
Internet Explorer imposes a time-out limit for the server to return data. By default, the time-out limit is as follows:
|Internet Explorer 4.0 and Internet Explorer 4.01||5 minutes|
|Internet Explorer 5.x and Internet Explorer 6.x||60 minutes|
|Internet Explorer 7 and Internet Explorer 8||60 minutes|
When the server is experiencing a problem, Internet Explorer does not wait endlessly for the server to return data.
Source : http://support.microsoft.com/kb/181050
Proposed Solution: Found some good links which gives some solutions which you can try [Frankly, Haven’t tried them on my own, try at your own risk! — I strongly recommend to use Firefox]
Now, we know what’s wrong with IE? But now the second question comes up Why it works with Firefox? Don’t worry we have answer for this as well.
Currently, Firefox timeout is determined by the system-level connection establishment timeout [Source : http://kb.mozillazine.org/Network.http.connect.timeout]. It was earlier issue in Firefox as well and they fixed it – https://bugzilla.mozilla.org/show_bug.cgi?id=592284
If you would like to know what your System-level connection is, please refer : http://support.microsoft.com/default.aspx?scid=kb;en-us;314053 [Source: https://bugzilla.mozilla.org/show_bug.cgi?id=142326]
Summary : When you have long running operation running on server and would like to run it from browser and if browser is displaying client side error, Firefox is a good choice!
Happy Long running operation! 🙂