I came across
this thread for setting other transparent proxy or, more generally, HTTP applications, which are not supported by default, to Web Shield.
However, I had been using
this way, which allows users to add process names of applications which communicate through HTTP traffic to be monitored by Web Shield.
I am using a transparant proxy for almost every HTTP communication and made Web Shield to monitor it through the latter method and letting the firewall application to monitor Web Shield. I like this method better but am I missing some possible drawbacks?
Also, if there are no faults, how about letting users to use the interface to do the same thing just like with the port, in future?
