httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16426] - Ignoring user abort
Date Fri, 31 Jan 2003 18:44:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16426>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16426

Ignoring user abort

neil@mpfreescene.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From neil@mpfreescene.com  2003-01-31 18:44 -------
That is a different error completely, I quote the following text from the top 
of that bug report from php.net

"
It seems that when a script terminates due to a
timeout connection_status() returns 0 (and
connection_timeout() no longer exists).

When aborted by a user connection_status() does return 1.
"


Paying close attention to the last sentance, when aborted by a user 
connection_status() does return 1, so the fault submitted there is problems for 
the TIMEOUT call, not ABORTED, the ABORTED function works in php as stateted 
there.


Like I already said, it works perfectly with apache 1.x, but has never worked 
with apache 2.x.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message