www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: os-solaris/3467: Broken client connections not detected
Date Wed, 02 Dec 1998 06:50:01 GMT
The following reply was made to PR os-solaris/3467; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: "Christopher W. Curtis" <ccurtis@aet-usa.com>
Cc: Apache bugs database <apbugs@apache.org>
Subject: Re: os-solaris/3467: Broken client connections not detected
Date: Tue, 1 Dec 1998 22:41:49 -0800 (PST)

 On Tue, 1 Dec 1998, Christopher W. Curtis wrote:
 > marc@apache.org wrote:
 > > 
 > > Synopsis: Broken client connections not detected
 > > 
 > > State-Changed-From-To: open-feedback
 > > State-Changed-By: marc
 > > State-Changed-When: Tue Dec  1 09:22:47 PST 1998
 > > State-Changed-Why:
 > >
 > > Do you have any reason for thinking this is an Apache issue
 > > and not a PHP issue?
 > I posted it to the PHP list, but it seems unlikely to me that PHP would
 > be it.  PHP does not patch anything in Apache, and I am 99.997% sure
 > that PHP is using the Apache-style read/write calls (PHP implements
 Yea, but it can do it wrong.
 > flush() because Apache buffers writes...).  I looked at the code in
 > http_main.c and think I know where the signal is being ignored, but I'm
 > not familiar enough with the internals to know why everything happening
 > in there that is.  It does appear to make sense to ignore the signal,
 > but for some reason the child is not exiting gracefully when it should. 
 If it is inside an ap_soft_timeout then php needs to be checking
 r->connection->aborted and the return value from the write functions.
 There are many many modules that do handle this properly.

View raw message