Andrew Steets schrieb:
I'm inclined to agree with you that the current behavior is a bug, but it
raises the question: should there be such a function that says "this
connection wasn't handled, don't even log it" - or, should ALL connections
always be logged, even if it's aborted?
As Scott suggested, we should probably log everything, at least for
some reasonable value of "everything." Even if you switch the access
log trace to the cleanup callback, you still don't get access entries
for clients who connect but don't issue a well formed HTTP request. I
don't have a huge problem with that, and I think it would be difficult
to log those types of events.
i am as well in favor of loging the adp_aborts, since this seems a used
idiom.
There is no advantage in omitting such entries in the log file, but it
might be
hard to figure out what happens without that.
For example, in our production system, we use nginx, which logs these
requests on its own. A problem show up, when we try to debug a situation,
where some requests present in the nginx log are missing in the
aolserver log.
-gustaf neumann
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<lists...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<lists...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
