bugzilla at apache
Nov 30, 2009, 3:08 AM
Post #1 of 1
(179 views)
Permalink
|
|
[Bug 48301] New: Feature request: improved connection status reporting
|
|
https://issues.apache.org/bugzilla/show_bug.cgi?id=48301
Summary: Feature request: improved connection status reporting
Product: Apache httpd-2
Version: 2.2.14
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: mod_log_config
AssignedTo: bugs [at] httpd
ReportedBy: ajp.sheppard [at] gmail
Currently the LogFormat and CustomLog directives support the "%X" format string
which indicates the connection status when response is completed.
This format string is extremely useful for determining how the end user
accessing a site is served, especially for requests that have a potential to
fail - such as long running request/response that generate a large amount of
content (e.g. downloading a large file).
The problem is that the %X directive does not provide enough granulatity to
indicate whether the connection was aborted by the client side or by the server
(Apache) side.
This is a very important metric as web analysts need to be able to distinguish
if the failure of an end user to receive a response is due to an issue on the
Apache side (e.g. due a possible configuration issue such as a low TimeOut
value) or due to the client aborting or canceling. An initial examination of
the code indicates that it is possible to clearly distinguish these two cases.
I suggest the following modification to connection status when the response
completes:
X = connection aborted by the SERVER before the response completed.
x = connection aborted by CLIENT side the before the response completed.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe [at] httpd
For additional commands, e-mail: bugs-help [at] httpd
|
