[IAG] Customized URL does not take effect – (matching relationship between custom URL and built-in URL library)

Problem Description

The custom URL is allowed to access imgcache.qq.com, but access is still denied

Process——

1. In the URL classification library, you can see that the website can recognize custom URLs
   
   294055b6d099ccf8a8.png (31.79 KB)
2. Check the policy set that the user matches, as shown below
   
   231245b6d0a147ca74.png (103.63 KB)

Root cause

Because the above policy has a built-in URL group that rejects entertainment information, it cannot match the following custom URL group.

solution

Move the policy for allowing custom URL groups to the top to solve the problem

Suggestions and Conclusion

There is no priority difference between custom URLs and built-in URLs. It depends on how the policy is called.
The built-in URL policy is rejected above, and the custom URL policy is allowed below. If the custom URL does not match, it will be rejected directly.
The principle of permission policy is that if a connection matches the permission or rejection rule, it will not proceed further.

Original Link

https://support.sangfor.com.cn/cases/list?product_id=22&type=1&category_id=6254&isOpen=true