[Bug 64730] New: Client hangup causes incorrect http status 500 logged

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 64730] New: Client hangup causes incorrect http status 500 logged

Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=64730

            Bug ID: 64730
           Summary: Client hangup causes incorrect http status 500 logged
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_fcgid
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

When a client resets the connection to the server while fcgid is still serving
a request, the following is logged:

[fcgid:warn] [pid 8218] (104)Connection reset by peer: [client a.b.c.d:57986]
mod_fcgid: ap_pass_brigade failed in handle_request_ipc function

In the access log this request is logged as a 500 internal server error. This
is incorrect: the response code is already sent to the client and probably not
a 500.

Steps to reproduce:

Create an fcgi script which does the following:
1) generate a "302 moved" response code, redirecting the client to another url
2) flush the response code to the fcgi daemon. Can be achieved by sending a
very large response body.
3) linger around for a while, don't finish up this request too quickly.

The client will parse the redirect, close the connection and go the the
indicated url.
The closed connection causes the warning in the server error log and the 500
response code in the access log.

What do I expect:

a) don't log a warning. It's not indicative of a situation which requires
attention. Logging as "info" is good enough.
b) log the correct response code in the access log

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 64730] Client hangup causes incorrect http status 500 logged

Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=64730

Erik Hensema <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from Erik Hensema <[hidden email]> ---
This bug seems to be already fixed in the development version.

Please make a new release so this bug finally gets fixed in a non-dev version
:)

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 64730] Client hangup causes incorrect http status 500 logged

Bugzilla from bugzilla@apache.org
In reply to this post by Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=64730

--- Comment #2 from Henry van Megen <[hidden email]> ---
Created attachment 37445
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37445&action=edit
Wireshark confirmation of connection reset

A screenshot of wireshark and a part of the logfile containing the warning. You
can see the connection RST in wireshark where the client disconnects as matched
to the log line where Apache logged the ap_pass_brigade warning.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]