How to disable the "Connection was reset" error pages that replace a partially loaded but otherwise readable page on poor connections?
I use a very unreliable, slow, high latency 2G mobile connection. This often results in a "Connection was reset" error page replacing the loading page. This is more often a nuisance than a help as the partially loaded page has often loaded to the point where it is quite readable albeit not complete or fully formatted but is then replaced with the error page. I find I often have to just hit the stop loading button just to be able to read the partially loaded page rather than risk FF popping up the error page and obliterating what I have loaded so far. Is there a simple entry in the config data to prevent these error pages from popping up and basically just let the page "hang" at wherever it got to as was the case in the early days of most browsers? Or can I lengthen any time-out parameters to indefinite to better suit this very flaky but only internet access option I have available to me?
Alle antwoorden (4)
I do not think you can change the about:config in android, but you can try
Thanks, guigs2, I just realised that I may have made my query confusing by not mentioning that I was in fact referring to the desktop version of FF not the Android one (it is just a 2G router). I will have a play with that script timeout you mentioned. I figured that timeouts might be the work-around if indeed those error pages are a permanent fixture in the FF design for whatever reason.
Hi Plastic_Inevitable, If it is not a time out issue, we are happy to further investigate as well.
Thanks guigs2. I have had a play with that script timeout parameter and it has no effect on the error page. I think that setting the parameter to 0 effectively makes the timeout unlimited too. I am pretty certain tho that the errors that trigger these FF error pages come from down at the network layer and just relate to unanswered packets etc which are commonplace on a poor connection. Unresponsive scripts up at the app layer from memory give errors about "script not responding, do you want to continue?" Being on a low bandwidth connection I filter out most extraneous scripts with NoScript anyway. I can get the error on a very basic and script free page when connection is poor. So while FF might have no control over what is going on down at the network level, I think there should be a way to prevent the display of these somewhat "destructive" pages when there is a network level error. A simple status bar message or dismissable pop-up error box would leave the current state of the page intact. Even rendering the error page as a new page so that the back button can be used to get back to the original page might be good. regards
kim