DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19889>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19889 CustomLog not correctly processing env=!xxx statement Summary: CustomLog not correctly processing env=!xxx statement Product: Apache httpd-2.0 Version: 2.0.36 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: mod_log_config AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Linux 2.4.18 Kernel. Attempting to isolate Virus messages into a separate logfile from access_log. Following statements are at the bottom of my httpd.conf file LogFormat "%h %l %u %t \"%r\" %>s %b" common SetEnvIf Request_URI "^/default.ida" attacks CustomLog logs/attack_log common env=attacks CustomLog logs/access_log common env=!attacks The results of the above statments are as follows: 1. The bad data from the Code Red virus IS being put into the attack_log file. 2. The access_log file is ALSO getting the virus data in it at the same time. This is not what I expected based on the second CustomLog statement. I have tried to switch the two CustomLog statements around but I get the same incorrect results. I did send a copy of this information to the Mailing list [email protected] on 5/8/03 but since no one responded to it, I'm hoping that you could tell me if I'm doing something incorrect or if there is a problem with the code. Any testing that you wish me to do, I will be glad to oblige. Thank you for your assistance in this matter. Frank Krauss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
