ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000451ClearOSapp-antivirus - Gateway Antiviruspublic2012-03-01 15:072012-12-03 17:46
Reporteruser2 
Assigned Touser2 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version6.4.0 Alpha 1Fixed in Version6.4.0 Alpha 1 
Summary0000451: Add support for upstream proxies
DescriptionIn some cases, ClearOS will be sitting behind a non-transparent proxy. For ClamAV updates, the following parameters can be set for this type of scenario:

HTTPProxyServer myproxy.com
HTTPProxyPort 1234
HTTPProxyUsername myusername
HTTPProxyPassword mypass

More information is available in this forum thread:
http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,26/func,view/id,37720/ [^]

These parameters should be set by the "clearsync" event system. This will change the parameters based on network proxy configuration in app-network. Like all clearsync implementations, it should be possible to easily disable the automagic.
TagsNo tags attached.
Attached Files

- Relationships
related to 0000449closeduser2 Add support for upstream proxies 
related to 0000450closeduser2 Add support for upstream proxies 
related to 0000452closed Add support for upstream proxies 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2012-03-01 15:07 user2 New Issue
2012-03-01 15:07 user2 Status new => acknowledged
2012-03-01 15:08 user2 Relationship added related to 0000449
2012-03-01 15:08 user2 Relationship added parent of 0000450
2012-03-01 15:14 user2 Relationship added child of 0000452
2012-03-21 08:35 user2 Relationship deleted parent of 0000450
2012-03-21 08:35 user2 Relationship added related to 0000450
2012-03-21 08:36 user2 Relationship deleted child of 0000452
2012-03-21 08:36 user2 Relationship added related to 0000452
2012-06-22 09:19 user2 Target Version 6.3.0 Beta 1 => 6.3.0
2012-07-03 08:03 user2 Target Version 6.3.0 => 6.4.0 Alpha 1
2012-11-16 19:58 user2 Status acknowledged => resolved
2012-11-16 19:58 user2 Fixed in Version => 6.4.0 Alpha 1
2012-11-16 19:58 user2 Resolution open => fixed
2012-11-16 19:58 user2 Assigned To => user2
2012-12-03 17:46 user2 Status resolved => closed