TRITON - Web Security Help, Version 7.7 - Websense

TroubleshootingIf a site uses post to send data to your Web server, Websense software does notrecognize keyword filtering settings for that URL. Unless your integration productrecognizes data sent via post, users can still access URLs containing blockedkeywords.To see whether a URL uses a post command, view the URL source from within yourbrowser. If the source code contains a string like “”, then post is usedto load that URL.Custom or limited access filter URLs are not filtered as expectedTRITON - Web Security Help | Web Security Solutions | Version 7.7.xIf an HTTPS URL in a limited access filter or custom URL list (recategorized orunfiltered) is not filtered as expected, an integration product may be transforming theURL 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:// is read as https://:443.When this occurs, Filtering Service cannot match the URL received from theintegration product with a custom URL or limited access filter, and does not filter thesite appropriately.To work around this problem, add both the IP addresses and URLs for sites you wantto filter using custom URLs or limited access filters.An FTP request is not blocked as expectedTRITON - Web Security Help | Web Security Solutions | Version 7.7.xWhen integrated with Check Point ® firewalls, Websense software requires folderview to be enabled in the client’s browser to recognize and filter FTP requests.When folder view is not enabled, FTP requests sent to the FireWall-1 proxy are sent toWebsense software with an “http://” prefix. As a result, Websense software filtersthese requests as HTTP requests, rather than FTP requests.Websense software is not applying user or group policiesTRITON - Web Security Help | Web Security Solutions | Version 7.7.xUsers may not be filtered by the user or group policy you assigned for a variety ofreasons. Check the following topics, and search the Knowledge Base for additionalinformation. User Service is not available, page 457 Remote users are not filtered by correct policy, page 460 Directory service connectivity and configuration, page 468 Directory service configuration in TRITON - Web Security, page 469 User identification and Windows Server 2008, page 469TRITON - Web Security Help 459