Joshua:
Yep, in lieu of an automated "inline" way to do it, I'll just have to
strip them out by hand (or grow a mental blindspot to them :-). Since
the IP and hostname does vary every time the DHCP lease expires, it
means there's no backend way at all I could automate it. The only means
of automation would be by comparing the server IP to the requesting IP
at the time of the request, and rejecting any that match.
I just wanted to do it to eliminate needless clutter from the log and
make it easier to scan the useful stuff.
Mark
Joshua Slive wrote:
On 5/3/07, Mark A. Craig <[EMAIL PROTECTED]> wrote:
Joshua:
Yes, I'd seen that, but my situation is a bit more complicated, since
the server isn't sitting at a static IP, and I wasn't entirely certain
how to do it. Would something like this work?
SetEnvIf Remote_Addr Server_Addr dontlog
CustomLog logs/access.log common env=!dontlog
No, that won't work.
I don't know of any way of matching a dynamic IP like that. Why don't
you just filter your logs after-the-fact? That is much simpler and
more efficient.
Joshua.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
