The way the policy tester works is by actually running requests through the httpproxy, therefore it can only be used to test requests that get handled by the proxy.
If you have a Filter Profile that only is for Endpoint Groups and does not have any Allowed Networks then it is not enforced by httpproxy and therefore cannot be tested by it.
Policies that are for Endpoints only are enforced by the Endpoint.
You can (if you want) include a single host (fake IP address) into the Allowed Networks of a Filter Profile so that you can test policies in the profile.
If you wish to test Endpoint-only profiles, please submit a feature request.
The way the policy tester works is by actually running requests through the httpproxy, therefore it can only be used to test requests that get handled by the proxy.
If you have a Filter Profile that only is for Endpoint Groups and does not have any Allowed Networks then it is not enforced by httpproxy and therefore cannot be tested by it.
Policies that are for Endpoints only are enforced by the Endpoint.
You can (if you want) include a single host (fake IP address) into the Allowed Networks of a Filter Profile so that you can test policies in the profile.
If you wish to test Endpoint-only profiles, please submit a feature request.
It is now possible to specify different HTTP authentication methods for different devices! Using identification agent scanning, UTM can now detect Windows, Mac OSX, Linux, iOS, Android, Blackberry and Kindle devices, and let you have filtering profiles based on this. For example, you can apply special filtering for all iPads in a school which uses a different method than the normal windows workstations.
it should also be possible the select a different agent for web filtering policy testing.
