On Thu, 2009-03-26 at 14:40 -0400, Dossy Shiobara wrote: > On 3/26/09 1:31 PM, Andrew Steets wrote: > > Hello, > > > > There are certain cases where connections probably ought to generate > > access log entries but do not. Specifically if an ADP exits via > > ns_adp_abort no access log entry will be generated, but data may have > > been returned to the client. This seems like a bug. > > I wonder - should this be the documented known behavior of ns_adp_abort > vs. ns_adp_return? i.e., abort indicates that the connection is > intentionally terminated, not logged, etc. vs. ns_adp_return which halts > ADP processing but continues the connection, which includes logging, etc. > > 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?
I would think that an aborted connection isn't a complete connection, and shouldn't require logging. Maybe something in the error log, but you can do that just before you call ns_adp_abort. Under what conditions should ns_adp_abort be used? Does calling this actually close a connection, or does it just remove what is in the buffer? tom jackson -- 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.
