Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 87937 invoked from network); 19 Apr 2004 23:35:12 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 19 Apr 2004 23:35:12 -0000 Received: (qmail 44721 invoked by uid 500); 19 Apr 2004 23:34:56 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 44522 invoked by uid 500); 19 Apr 2004 23:34:55 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Apache HTTPD Bugs Notification List" Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 44496 invoked from network); 19 Apr 2004 23:34:54 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 19 Apr 2004 23:34:54 -0000 Received: (qmail 11717 invoked by uid 50); 19 Apr 2004 23:35:48 -0000 Date: 19 Apr 2004 23:35:48 -0000 Message-ID: <20040419233548.11716.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 28478] - SEARCH log-entries X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28478 SEARCH log-entries slive@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From slive@apache.org 2004-04-19 23:35 ------- This is a support request, not a bug report, and as such should be directed to a user support forum such as http://httpd.apache.org/userslist.html But to give you a little preview: - No, there is no way internally to apache to exclude SEARCH requests from the logs. - Doing so isn't, in general, a good idea anyway, since complete logs are a webmasters best friend. How else are you supposed to tell what is happening to your server? - You can limit the size of the log entries using the LimitRequestLine directive, but be sure to keep this long enough to handle the longest normal request you expect to receive. - You should be managing the size of your logs by rotating them on a regular basis and you can take out anything you don't want in them at the same time you rotate them. - The Deny... directives do indeed exclude SEARCHes, but they only exclude them from accessing the server, not from being logged. There is a bug in the manner in which these requests are being logged, but since the bug may have minor security implications, it is being discussed on a private mailing list, not in the bug database. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org