You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/10/10 15:02:36 UTC

DO NOT REPLY [Bug 23065] - CGI/FastCGI Appl. gets no signal on User Abort

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=23065>.
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=23065

CGI/FastCGI Appl. gets no signal on User Abort

trawick@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From trawick@apache.org  2003-10-10 13:02 -------
This fix, committed to the Apache 2 stable branch for release with the upcoming
Apache 2.0.48, seems to cover this situation:

  *) mod_deflate: Don't attempt to hold all of the response until we're
     done.  [Justin Erenkrantz]

Because mod_deflate was buffering the response internally, Apache didn't try to
write to the client connection as soon as it should have.  Trying to write to
the client connection is how we find out that the client pressed STOP.

Go to http://cvs.apache.org/viewcvs.cgi/httpd-2.0/modules/filters/mod_deflate.c
and download the link that says "1.26.2.8" to grab the latest stable mod_deflate
, which has this fix.

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