Question about Application control and web filtering

Time-Based Application Control Rules are currently under review as a feature request:
Web Security: Time-Based Application Control Rules

When you activate Web Filtering you can manage Default Web Filter Profile in that section. In "Web Filter Profiles" section you can add and manage additional Profiles.

Thanks for your answer.

My web filtering is on transparent, so i need is to redo the profile on the web profile filter
If i had activate some features that are not set on web profile filter (ex : no caching for an internal host) do i have to activate also the basic "web filter" ?

Finally what happen if both "web filtering" and "web profile filtering" is activated ?

Thanks

What is your UTM version, and can you post some screenshots about what have you done ?

If you ask about having multiple "Web Filter Profiles", look at my screenshot. "Default Web Filter Profile" is on the bottom (that is the one that you can manage from Web Filtering section) with lowest priority. I also created two additional Web profiles for Company and Wifi users.

Version is  9.111-7

Here are some screenshots

Ah, OK..sorry...in 9.2 graphic layout and some terminology changed...[:)]

Hi,

Ok but this doensn't bring an answer to my question

What is the behavior if both "web filtering" and "web profile filtering" is activated : The 2 features will work together ?

Not "together" as Application Control works with traffic allowed b Firewall or Web Filtering rules, so, for example, it can block traffic allowed by Web Filtering, but not allow traffic blocked by Web Filtering.

If i had activate some features that are not set on web profile filter (ex : no caching for an internal host) do i have to activate also the basic "web filter" ?

General caching behavior is regulated in 9.1 on the 'Advanced' tab.  If it's not enabled there, then your Exception has no effect.

Cheers - Bob

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