SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0002702: Truncated and incorrect entries in content filter log (logs_dansguardian.cgi) - MantisBT
MantisBT - Endian Firewall
View Issue Details
0002702Endian FirewallGUIpublic2010-02-19 10:442010-11-22 12:08
deryk 
peter-endian 
normalmajoralways
closedfixed 
2.3 
2.4.1 
0002702: Truncated and incorrect entries in content filter log (logs_dansguardian.cgi)
When viewing /cgi-bin/logs_dansguardian.cgi the output comes out as follows (example line):

2010/Feb/01 08:53:02 192.168.0.2 (127.0.0.) http://news.google.co [^] ok

This is on the 19th of Feb, 08:53:20, from 192.168.0.23 to news.google.com - but each column is being truncated by 1 character. This also prevents it from correctly detecting the word "denied".

The correct output should be:

2010/Feb/19 08:53:20 192.168.0.23 (127.0.0.1) http://news.google.com [^] DENIED
To fix the issue, go to line 164 of /home/httpd/cgi-bin/logs_dansguardian.cgi

Where it reads:
split(/[^,]\s+/, $line);

Change it to:
split(/\s+/, $line);
No tags attached.
Issue History
2010-02-19 10:44derykNew Issue
2010-02-19 10:51derykNote Added: 0003821
2010-02-19 10:53derykNote Edited: 0003821
2010-03-04 21:13peter-endianNote Added: 0003934
2010-03-04 21:13peter-endianStatusnew => resolved
2010-03-04 21:13peter-endianFixed in Version => 2.3.1
2010-03-04 21:13peter-endianResolutionopen => fixed
2010-03-04 21:13peter-endianAssigned To => peter-endian
2010-11-22 12:08peter-endianFixed in Version2.3.1 => 2.4.1
2010-11-22 12:08peter-endianStatusresolved => closed

Notes
(0003821)
deryk   
2010-02-19 10:51   
(edited on: 2010-02-19 10:53)
BTW I marked this as major because user of 192.168.0.2 (for example) could potentially face reprisal from their company for visiting a site that was actually visited by 192.168.0.23. This is my first bug report so correct me if this is the wrong way to evaluate it.

(0003934)
peter-endian   
2010-03-04 21:13   
applied. thank you for the fix!