Bugs item #459740, was opened at 2001-09-07 22:43
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=103152&aid=459740&group_id=3152
Category: Architecture: Server (nsd)
Group: aolserver3_3
Status: Open
Resolution: None
Priority: 5
Submitted By: Jerry Asher (jerryasher)
Assigned to: Nobody/Anonymous (nobody)
Summary: nssock/socksendfd doesn't set ncontent
Initial Comment:
neither nssock/socksendfd nor nsunix/drvsendfd appear
to set the connection ncontentsent value.
This causes erroneous logging.
Empirically, I *know* that nsunix/drvsendfd does not
set the value. This led me to a code inspection of
nssock/socksendfd.
Now, I don't know which platforms actually support
nssock/socksendfd, since it required a compile time
#def HAVE_SENDV, but those platforms that do have it,
will not log the content sent length correctly...
----------------------------------------------------------------------
>Comment By: Jerry Asher (jerryasher)
Date: 2001-09-07 23:10
Message:
Logged In: YES
user_id=20647
I believe the problem is within Ns_ConnSendFd. That is the
last routine that has authority and access to set the
nContentSent field. I've attached a patch to do just that
just before it calls the underlying socket driver's sendfd
routine.
Now the real question is where the sendfd routine makes any
sense at all...
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=103152&aid=459740&group_id=3152
