What are the types of timeout and how to set the correct one
I have a Firefox and when accessing a domian that times out sometimes very fast.
The types of timeout (about:config) are not described there. Is there a description?
And is there a list of other "connection error problems" that FF is displaying (like "Server not found", ...) and what is the reason for them?
所有回覆 (8)
What security software are you using and what site is that it is timing out?
You appear to be using an old and no longer supported Firefox 47 version.
The System Details list shows you run an older Firefox version that is no longer supported with security updates. Any specific reason for not updating?
- User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Please update to the current Firefox 61.0.2 release.
- Help -> About Firefox
- https://support.mozilla.org/en-US/kb/update-firefox-latest-version
Do you mean that you are disconnected or need to login again or does something else go wrong?
I don't think that you can modify a pref on the about:config page to prevent a website from timing out. Make sure that your clock has the correct time and date.
Paul.FE said
I have Firefox and when accessing a domain that times out sometimes very fast. The types of timeout (about:config) are not described there. Is there a description?...
What you're looking for is different what from what I did long ago. I was shortening a timeout. You wish to lengthen one.
Your timing-out 'very fast' may have to with using a very old, out-dated, browser, as cor-el pointed-out, with no more security support. Browsers update for security and modern Website functionality that breaks with using older browsers.
A very old computer with an old, out-dated browser equates to security risks and problems piling-up when surfing to 'modern' Websites. It was pain and frustration I had gone through many, many years ago and had to bite the bullet and get a newer computer and go to an up-to-date browser.
No way around it. Technology moves on. You can't 'protest' and sit in the 'out-dated chair' anymore.
Having said that, you can try at your own risk below:
I played around with a timeout config a while back when I got the 'ghost' browser screen. I believe I shortened the timeout for that so I wouldn't have to wait for the default timeout. I rarely see it anymore.
In About:Config, here are some Search Terms you can try (Then sort the 'Value' Field to look through the numeric values first):
network.http.connection ghost network. timeout
These are the defaults I worked with before:
network.http.connection-timeout 90 memory.ghost_window_timeout_seconds 60
But, you're looking to lengthen something, so you'll have to find something else with the above About:Config Search to play around with at your own risk, if there's such a setting to begin with to 'stop your quick time-out'.
There's a bunch of other 'network timeout' values that I never fooled with.
~Pj
"Server not found" sounds like a DNS lookup returned no match. It doesn't sound like a timing issue.
WestEnd said
What security software are you using and what site is that it is timing out?
No security software and the site does not matter - it is about firefox.
cor-el said
You appear to be using an old and no longer supported Firefox 47 version. Any specific reason for not updating?
I don't think that you can modify a pref on the about:config page to prevent a website from timing out.
Sorry I didn't mention the specific firefox version (I do NOT use 47) - but actual it does not matter what version cause it is similar for all (about:config + technical basics) . As well as reasons for not getting the wanted page (Server Not found -> maybe DNS problem, Connection timed out -> server did not respond)
jscher2000 said
"Server not found" sounds like a DNS lookup returned no match. It doesn't sound like a timing issue.
Sorry for mixing that up. Maybe I should have been opening two questions. 1: the Question for the description of the different timeout types/settings in the about:config 2: a list of optional errors for not geting the page (Server Not found -> maybe DNS problem, Connection timed out -> server did not respond)
Pj said
Your timing-out 'very fast' may have to with using a very old, out-dated, browser, as cor-el pointed-out, with no more security support. Browsers update for security and modern Website functionality that breaks with using older browsers.
A time-out does not depend on the version of the browser - maybe the time interval is set differently but time out is just because of no response - how should the version affect this? In regards to the question it does not matter what version.
Pj said
In About:Config, here are some Search Terms you can try (Then sort the 'Value' Field to look through the numeric values first): network.http.connection ghost network. timeout These are the defaults I worked with before: network.http.connection-timeout 90 memory.ghost_window_timeout_seconds 60 There's a bunch of other 'network timeout' values that I never fooled with. ~Pj
The actual problem is that there is no description - that is what I'm looking for not fooling around.
由 Paul.FE 於 修改
Current Firefox releases have some developer tools where you can check websites. There is for instance a DNS loopkup tool on the about:networking page (in Firefox 47 this page is probably vert basic). There is the Network Monitor as part of the developer toolbox that should work in Firefox 47 as well (check the Timings tab).
cor-el said
Current Firefox releases have some developer tools where you can check websites. There is for instance a DNS loopkup tool on the about:networking page (in Firefox 47 this page is probably vert basic). There is the Network Monitor as part of the developer toolbox that should work in Firefox 47 as well (check the Timings tab).
My goal is not to play around or debug anything. I would like to know what the settings of firefox are really intended to do.
Hundreds of reasons and all are subject to the individuals install of all software, add-ons/Extensions, Security Programs , Audio/Video and so forth that possibly does not apply to you.
So what is your issue so we can solve it please ?