https://bz.apache.org/bugzilla/show_bug.cgi?id=56188
Luca Toscano <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #34073|0 |1 is obsolete| | --- Comment #12 from Luca Toscano <[email protected]> --- Created attachment 34560 --> https://bz.apache.org/bugzilla/attachment.cgi?id=34560&action=edit Send FCGI_ABORT to the backend when the client disconnects Updated the patch with some trace error messages and a better handling of the response value rv. The 'dispatch' function checks the returned 'rv' value if not different from APR_SUCCESS, so the last one to return shouldn't always be the result of the send_data call for the FCGI_ABORT notification (that most of the times, if the backend is healthy, returns APR_SUCCESS). Remaining unclear points: 1) A 503 is logged with this patch, meanwhile a 200 was logged for the previous version. What is the best thing to log in case a client connection is aborted? 2) When ProxyTimeout is hit, should we send a FCGI_ABORT notification to the backend? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
