Re: [Bug 56188] mod_proxy_fcgi does not send FCGI_ABORT_REQUEST on client disconnect

On Thu, Feb 2, 2017 at 5:16 PM, Yann Ylavic wrote: > On Thu, Feb 2, 2017 at 4:51 PM, Luca Toscano wrote: >> >> 2017-01-30 21:58 GMT+01:00 Yann Ylavic : >>> >>> Maybe what is missing is nonblocking reads on the backend side, and

Re: [Bug 56188] mod_proxy_fcgi does not send FCGI_ABORT_REQUEST on client disconnect

On Thu, Feb 2, 2017 at 4:51 PM, Luca Toscano wrote: > > 2017-01-30 21:58 GMT+01:00 Yann Ylavic : >> >> Maybe what is missing is nonblocking reads on the backend side, and on >> EAGAIN flush on the client side to detect potential socket errors? > >

Re: [Bug 56188] mod_proxy_fcgi does not send FCGI_ABORT_REQUEST on client disconnect

2017-01-30 21:58 GMT+01:00 Yann Ylavic : > On Mon, Jan 30, 2017 at 7:17 PM, Luca Toscano > wrote: > > > > The use case that I had (the one that caused me to check the original > > bugzilla task/patch and work on it) was a long running PHP script >

Re: [Bug 56188] mod_proxy_fcgi does not send FCGI_ABORT_REQUEST on client disconnect

On Mon, Jan 30, 2017 at 7:17 PM, Luca Toscano wrote: > > The use case that I had (the one that caused me to check the original > bugzilla task/patch and work on it) was a long running PHP script (running > on HHVM) that wasn't returning anything until the end of the job

Re: [Bug 56188] mod_proxy_fcgi does not send FCGI_ABORT_REQUEST on client disconnect

2017-01-30 15:15 GMT+01:00 Yann Ylavic : > Hi Luca, > > continuing on dev@... > > On Mon, Jan 30, 2017 at 11:42 AM, wrote: > > https://bz.apache.org/bugzilla/show_bug.cgi?id=56188 > [] > > > > My question was if there was any corner case in which if,

Re: [Bug 56188] mod_proxy_fcgi does not send FCGI_ABORT_REQUEST on client disconnect

Hi Luca, continuing on dev@... On Mon, Jan 30, 2017 at 11:42 AM, wrote: > https://bz.apache.org/bugzilla/show_bug.cgi?id=56188 [] > > My question was if there was any corner case in which if, after a client has > initiated a TCP connection close, mod-proxy-fcgi wrongly