www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Matuschek <daniel.matusc...@tesion.de>
Subject Re: general/3869: Server doesn't close connections after timeout period
Date Fri, 12 Feb 1999 09:10:01 GMT
The following reply was made to PR general/3869; it has been noted by GNATS.

From: Daniel Matuschek <daniel.matuschek@tesion.de>
To: "'lars@apache.org'" <lars@apache.org>, apache-bugdb@apache.org,
        Daniel Matuschek <daniel.matuschek@tesion.de>
Cc: "'apbugs@Apache.Org'" <apbugs@apache.org>
Subject: Re: general/3869: Server doesn't close connections after timeout 
	period
Date: Fri, 12 Feb 1999 08:50:19 +0100

 Hi Lars,
 
 maybe you looked at the server when it was night in Germany -=20
 then there is not much traffic.
 Please try telneting to port 80 and let the telnet session be=20
 opened for a while without doing something. Server timeout is=20
 set to 10 seconds. Thus, the server should close the=20
 connection after 10 seconds, but nothing happens.=20
 
 Daniel
 
 -----Urspr=FCngliche Nachricht-----
 Von: lars@apache.org [mailto:lars@apache.org]
 Gesendet am: Donnerstag, 11. Februar 1999 21:17
 An: apache-bugdb@apache.org; daniel.matuschek@tesion.de; =
 lars@apache.org
 Betreff: Re: general/3869: Server doesn't close connections after
 timeout period
 
 [In order for any reply to be added to the PR database, ]
 [you need to include <apbugs@Apache.Org> in the Cc line ]
 [and leave the subject line UNCHANGED.  This is not done]
 [automatically because of the potential for mail loops. ]
 [If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request ]
 [from a developer.                                      ]
 [Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 
 
 Synopsis: Server doesn't close connections after timeout period
 
 State-Changed-From-To: open-feedback
 State-Changed-By: lars
 State-Changed-When: Thu Feb 11 12:17:09 PST 1999
 State-Changed-Why:
 
 I don't see anything unusual in your server-status.
 
 Looks pretty normal...
 Severity-Changed-From-To: serious-non-critical
 Severity-Changed-By: lars
 Severity-Changed-When: Thu Feb 11 12:17:09 PST 1999

Mime
View raw message