New features:

  • Log file management.
  • Fail-over for routing rules.
  • Ability to send a backup copy of the setting to the administrator either via email or FTP. The backup can be set to be delivered on a daily, weekly or monthly schedule.
  • Source-based routing.
  • Implemented ability to specify interface in routing rule.
  • Ability to change the port that the proxy listens to. By default this is port 3128.



  • Updated the Active Directory connection testing tool to be more accurate.
  • You now can reorder the routing rules all from the WebAdmin.
  • The routing rule will also specify the source IP to be selected for a packet. The IP will be based on the interface specified.
  • Previously some of the error pages from ProxyNow! (e.g. if the page is blacklisted or the page extension is blocked) would redirect you to “localhost”. This will cause a problem when ProxyNow! is used in transparent proxy mode since “localhost” would result in the browser to access the local web server. This normally means the user will see the IIS (Internet Information Server) page. This issue has now been fixed. No more redirection to “localhost”. Instead “rewriting” is used.



  • Fixed the display of the total hard disk space in the web admin for the new 2013 ProxyNow! appliance hardware
  • Fixed the issue whereby the Web Usage report with custom date will not show any data
  • Fixed the issue whereby the gateway is not display when you edit an old routing rule (i.e. a rule created before we support multiple gateways).
  • Fixed the issue where iptables needed to be reloaded manually after a link fail-over detected
  • Fixed an issue with the log file management where the backend daemon not started automatically resulting in failure to manually delete or download the log files.
  • Fixed an issue where if you have a blacklist/whitelist with 2 URLs where one is a subdomain of another, squid will not accept this configuration and refuses to start. e.g if you have 2 URL, one being a subdomain like and the other being the parent domain now what we do is that we remove the subdomain (i.e. in this example) as it is not necessary.
  • Fixed an issue with the feature to “block by extension”. Previously ProxyNow! was not checking just the extension but the full URL. So as a result, it might have blocked unintended sites.