> > Is it possible to log incoming connections that don't send any
data?
>
> Don't think so... HTTP is an application that sits on top of TCP/IP.
So
> the session is established at the TCP/IP layer and the server is
ready
> to pipe any incoming data to apache. But, at this point, apache is
> unaware of the connection so cannot log it or anything. Only when the
> client sends a request (is that what you mean by "data"?) does apache
> realise there is anybody there.
> The logging phase is more or less the last phase within the apache
> request lifecycle. Without "data", there is not request, thus no
> lifecycle and thus no logging.
> I believe this has been discussed here recently within the following
> thread:
> http://marc.info/?t=119539991500001&r=1&w=2
> Don't think they have found a solution though. I gave up somewhere
along the line.
> regs,
> Christian
Theoretically, I think it should be possible for Apache to log an entry when accept() call returns and before it issues first read() call on socket. Log entry then should be made after read timeout. In such cases, there is nothing to be logged except remote IP and timestamp.
We monitored TCP connections by periodically running "netstat -pant" command and grepping for httpd port and counting connections in each of "ESTABLISHED SYN_SENT SYN_RECV FIN_WAIT1" etc. states.
HTH,
Sameer
____________________________________________________________________________________
Be a better pen pal.
Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|