Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Policy enforcement issues > Custom or limited access filter URLs are not handled as expected
Custom or limited access filter URLs are not handled as expected
Web Security Help | Web Security Solutions | Version 7.8.x
If an HTTPS URL in a limited access filter or custom URL list (recategorized or unfiltered) is not blocked or permitted as expected, an integration product may be transforming the URL into a format that Filtering Service cannot recognize.
Non-proxy integration products translate URLs from domain format into IP format. For example, the URL https://<domain.com> is read as https://<IP_address>:443. When this occurs, Filtering Service cannot match the URL received from the integration product with a custom URL or limited access filter, and does not manage the site appropriately.
To work around this problem, add both the IP addresses and URLs for sites you want to define as custom URLs or use in limited access filters.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Policy enforcement issues > Custom or limited access filter URLs are not handled as expected
Copyright 2016 Forcepoint LLC. All rights reserved.