https://bz.apache.org/bugzilla/show_bug.cgi?id=58118
Bug ID: 58118
Summary: mod_proxy_fcgi logs 503 when user aborts connection
Product: Apache httpd-2
Version: 2.4.12
Hardware: PC
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: mod_proxy_fcgi
Assignee: [email protected]
Reporter: [email protected]
Created attachment 32893
--> https://bz.apache.org/bugzilla/attachment.cgi?id=32893&action=edit
Patch
If the user aborts the connection, while mod_proxy_fcgi reads data from the
backend and pass it down the filter chain, ap_core_output_filter returns EPIPE
or ECONNABORTED which is returned by dispatch and interpreted by
fcgi_do_request in mod_proxy_fcgi as an backend failure and
HTTP_SERVICE_UNAVAILABLE is returned. This seems to be wrong since the fcgi
backend worked fine. There is also an inconsistency between what the client
(partially) recieved and what's logged.
I invested some time to retrace this behaviour. You can provoke it, when you
request a big file from the fcgi backend and abort the retrieval (e.g. use wget
on the CLI and Ctrl + C).
I want to propose a patch (see attachement), but please be aware that I'm
neither an experienced C-programmer nor ever submitted a patch to an open
source project. Having this in mind: The patch worked for me (built
successfully on SLES and tested it with the described procedure above). If
LogLevel is trace1 or lower it leads to a error-Log entry.
I don't know whether APLOGNO(001075) is the correct error number, I didn't find
the documentation under docs/log-message-tags/README (pointed to in
includes/httpd.h, 117)
If necessary I can provide further information.
Kind regards,
Tobias Adolph
--
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]
