Bug #60586 [Com]: ignore_user_abort=true has no effect on IIS with FastCGI

From: Date: Wed, 23 Aug 2017 20:46:52 +0000
Subject: Bug #60586 [Com]: ignore_user_abort=true has no effect on IIS with FastCGI
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-210786@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=60586&edit=1

 ID:                 60586
 Comment by:         gudang at gmail dot com
 Reported by:        sauvant at aspera dot com
 Summary:            ignore_user_abort=true has no effect on IIS with
                     FastCGI
 Status:             Open
 Type:               Bug
 Package:            IIS related
 Operating System:   Windows Server 2008 R2
 PHP Version:        5.3.8
 Block user comment: N
 Private report:     N

 New Comment:

Hello, i'm still having this issue even on newer PHP versions


Previous Comments:
------------------------------------------------------------------------
[2013-09-11 21:41:54] curibe at microsoft dot com

We investigated this issue from an IIS perspective by reproducing the issue using the sample page
listed in this bug and setting ignore_user_abort=true we saw the following behavior:
Shortly after the browser disconnects, we get a failure on the named pipe connection to the
php-cgi.exe process indicating that pipe was disconnected.  That takes us to a path that terminates
that process.  We do this because, once the FastCGI process has disconnected, we can no longer
manage it.  To prevent it from consuming system resources, we terminate it.  This is all by design,
and it may be different on other web servers if they allow processes to run after they’ve
disconnected.
We also verified that we are not closing the pipe on our side prior to terminating the process.  It
is definitely getting closed on the FastCGI process side.

------------------------------------------------------------------------
[2012-12-07 01:27:57] aharvey@php.net

A pull request or patch would be much appreciated, I'm sure. :)

------------------------------------------------------------------------
[2012-12-06 12:43:25] rainer at dueckerhoff dot de

This bug still persists in the latest 5.3 version after about a year of this bug 
report.
Any chance that it could be fixed or any explanation on why it doesn't work with 
IIS but with Apache (and thus cannot be fixed)? Or at least a workaround?

Cheers,
Rainer

------------------------------------------------------------------------
[2012-07-10 12:32:43] sauvant at aspera dot com

There is a thread at the IIS forum, too: http://forums.iis.net/t/1190270.aspx
No feedback at all :-(

Is the issue described PHP or IIS related? 
Any opinions?
Anybody able to reproduce?

Best regards
Keith

------------------------------------------------------------------------
[2012-06-25 15:00:50] lars_teuber at gmx dot de

Microsoft-IIS/7.5. Best regards, Lars.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=60586


--
Edit this bug report at https://bugs.php.net/bug.php?id=60586&edit=1


Thread (13 messages)

« previous php.bugs (#210786) next »