Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Server not responding timeout

121 views
Skip to first unread message

Lester Caine

unread,
Feb 21, 2008, 4:48:46 AM2/21/08
to
I have a niggle which is becoming annoying.
I know that the cause is probably the network, but I'd like to make Firefox
less susceptible to it.
I've got Apache/PHP generating pages with a 30 second refresh, and the content
is built depending on the number of people waiting to be served. Overnight
this is just 'No more waiting', but each morning one or two of currently 4
Linux boxes has the 'server has not responded' page, and just clicking on the
button restores operation.
I've found various tips and FAQ's on all sorts on these type of error, but I'm
not seeing anything appropriate. Where is the browser end timeout set? Is it
Firefox or Linux which is timing out? What settings should I be looking to
increase to hide the problem, which I am assuming is due to the network
becoming blocked by some overnight activity. As soon as the button is pressed
everything is back to normal, and as only one or two machines is affected I
don't think it's a server end problem?
Once I know the right question to ask the answer will be obvious :(

--
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php

quim.rovira

unread,
Feb 21, 2008, 10:52:19 AM2/21/08
to

I'm looking for the same answer... I've been checking the about:config
page in firefox, but did not find anything I'd trust to be such
parameter. I'll let you know if I find it anywhere!

Lester Caine

unread,
Feb 22, 2008, 4:03:52 AM2/22/08
to
quim.rovira wrote:
> On Feb 21, 10:48 am, Lester Caine <les...@lsces.co.uk> wrote:
>> I have a niggle which is becoming annoying.
>> I know that the cause is probably the network, but I'd like to make Firefox
>> less susceptible to it.
>> I've got Apache/PHP generating pages with a 30 second refresh, and the content
>> is built depending on the number of people waiting to be served. Overnight
>> this is just 'No more waiting', but each morning one or two of currently 4
>> Linux boxes has the 'server has not responded' page, and just clicking on the
>> button restores operation.
>> I've found various tips and FAQ's on all sorts on these type of error, but I'm
>> not seeing anything appropriate. Where is the browser end timeout set? Is it
>> Firefox or Linux which is timing out? What settings should I be looking to
>> increase to hide the problem, which I am assuming is due to the network
>> becoming blocked by some overnight activity. As soon as the button is pressed
>> everything is back to normal, and as only one or two machines is affected I
>> don't think it's a server end problem?
>> Once I know the right question to ask the answer will be obvious :(

> I'm looking for the same answer... I've been checking the about:config


> page in firefox, but did not find anything I'd trust to be such
> parameter. I'll let you know if I find it anywhere!

Please can someone explain what replaced
network.http.request.timeout
when it was removed from the code base

It seems that a message controlled by this timeout is being displayed, but
that there is no way of controlling it?

I'm trying to sort this for Firefox running on Linux.


--
Lester Caine - G8HFL
-----------------------------

Alex K.

unread,
Feb 23, 2008, 9:04:44 AM2/23/08
to

Note the following, in relation to network.http.connect.timeout:

http://kb.mozillazine.org/Network.http.connect.timeout#Background

"Background

This preference was one of several added to allow low-level tweaking of
the HTTP networking code. After a portion of the same code was
significantly rewritten in 2001, the preference ceased to have any
effect (as noted in all.js as early as September 2001).

Currently, the timeout is determined by the system-level connection
establishment timeout. Adding a way to configure this value is
considered low-priority."

See also:

https://bugzilla.mozilla.org/show_bug.cgi?id=205140
Bug 205140 – Prefs: remove "network.http.*.timeout"

https://bugzilla.mozilla.org/show_bug.cgi?id=205077
Bug 205077 – Prefs: Networking cleanup for trunk

https://bugzilla.mozilla.org/show_bug.cgi?id=142326
Bug 142326 – Conn: configurable http timeout in UI

--
Alex K.

0 new messages