SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-22 00:04 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0001159	ClearOS	app-content-filter - Content Filter	public	2013-05-24 10:00	2013-06-04 09:53
Reporter	user2
Assigned To	user2
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version	6.4.0 Updates	Fixed in Version	6.4.0 Updates
Summary	0001159: Banned sites prefixed with http:// end up in the banned URL list (instead of banned sites)
Description	The underlying DansGuardian configuration files split up banned "sites" and "URLs" into two different configuration files. For usability reasons, this distinction is not made in the GUI. When a user prefixes a banned site with http:// (e.g. http://example.com [^] instead of the documented way: example.com), the site ends up in the URL file. Clean this up.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000861) user2 2013-05-24 10:08	Source Code Changelog --------------------------------------------------- - Fixed http:// prefix handling for sites and URLs [tracker 0001159] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=6050 [^] U webconfig/apps/content_filter/trunk/libraries/DansGuardian.php

Notes

Issue History
Date Modified	Username	Field	Change
2013-05-24 10:00	user2	New Issue
2013-05-24 10:00	user2	Assigned To	=> user2
2013-05-24 10:00	user2	Status	new => confirmed
2013-05-24 10:08	user2	Checkin
2013-05-24 10:08	user2	Note Added: 0000861
2013-05-24 10:08	user2	Status	confirmed => resolved
2013-05-24 10:08	user2	Fixed in Version	=> 6.4.0 Updates
2013-05-24 10:08	user2	Resolution	open => fixed
2013-06-04 09:53	user2	Status	resolved => closed

Issue History