The source ip and mode (port number) determines which filter profile is used (first match wins).
The filter profile plus user authentication determines the policy that is applied.
The policy determines the filter action
The filter action detetmines if the request is allowed.
If the user does not match any policy, the default policy for that filter action is applied. It will not evaluate any additional filter profiles.
If no filter profile matches the request, I think the traffic is handled as not procied, so firewall rules are applied instead.
The source ip and mode (port number) determines which filter profile is used (first match wins).
The filter profile plus user authentication determines the policy that is applied.
The policy determines the filter action
The filter action detetmines if the request is allowed.
If the user does not match any policy, the default policy for that filter action is applied. It will not evaluate any additional filter profiles.
If no filter profile matches the request, I think the traffic is handled as not procied, so firewall rules are applied instead.
Thanks for bringing this thread back up, Doug. Your comments are exactly correct about how Web Filtering works.
In fact, the OP's question was more about how Application Control interacts with Web Filtering. My answer above was done in 2014, before FrankBarmentlo had me add Application Control to #2 in Rulz - and that's a clearer answer now to the question.
Cheers - Bob