HTTPS blocking when integrated with Squid

Applies to

Web Filter v7.6

Web Security v7.6

HTTPS blocking when integrated with Squid

To block HTTPS traffic, you must configure the Squid integration with one of these options:

Install Network Agent, the Websense component that performs protocol filtering, and configure it to block HTTPS traffic.

For instructions on installing Network Agent, see Installing Web Security components. See Deploying Network Agent for location information and the TRITON - Web Security Help for configuration instructions.

If Squid acts as a proxy server, you can configure it to filter all HTTPS traffic.

1.	Go to the /etc/wsLib/ directory and open the wsSquid.ini file in a text editor.

2.	Under initSection, change the value of UseHTTPSBlockPage to yes.

The default setting is no, which causes Squid to permit all HTTPS traffic.

3.	Save your changes.

4.	Restart Squid Web Proxy Cache.

All requests for HTTPS pages are filtered, but if a request is blocked, Squid Web Proxy Cache sends a Squid-generated error page to the user. Users do not see the Websense block page, because Squid Web Proxy Cache is unable to deliver it.

 

Note  In some cases, when HTTPS is blocked, the Websense block page may be delivered to the user's browser, or a blank page is displayed, instead of the Squid-generated error page. Regardless, HTTPS is filtered properly. If a request should be blocked, it is blocked.