Configuring Interaction between Dr.Web ICAPD and Squid |
General scheme of interaction between a Squid proxy server, drweb-icapd and a client is as follows: Figure 16. General interaction scheme In this scheme, a client interacts with an HTTP server through a proxy server. The proxy server is a client of the ICAP server (Dr.Web ICAPD). Dr.Web ICAPD module, in turn, is a client of Dr.Web Daemon. Dr.Web ICAPD allows to perform virus scanning (using Dr.Web Daemon) of all HTTP traffic coming from the HTTP server and transmitted by the proxy server via the ICAP protocol. The given scheme does not allow FTP traffic scanning. For details on how to enable scanning of FTP traffic, refer to the Configuring Squid to Scan FTP Traffic section. Note that HTTPS traffic is not scanned as it is encrypted and cannot be decrypted without the public key of the HTTPS server. To enable Squid to use Dr.Web ICAPD, edit the squid.conf configuration file (usually located at /usr/local/squid/etc) to allow usage of the ICAP protocol. For this purpose, uncomment the lines mentioned below and edit the specified default values if necessary. If the lines are not present, add them to the end of the configuration file: 1. Enable usage of the ICAP protocol: icap_enable on 2. Register new ICAP service: For Squid 3.0: icap_service service_1 respmod_precache 0 icap://127.0.0.1:1344/respmod For Squid 3.1: icap_service service_1 respmod_precache bypass=0 icap://127.0.0.1:1344/respmod
When ICAP preview mode is enabled, configure additional settings. 3. Enable the ICAP preview mode: icap_preview_enable on 4. Specify size of the message (in bytes) sent to ICAP preview: icap_preview_size 0
5. If necessary, enable logging the IP address of the client that requested resource: icap_send_client_ip on 6. If necessary, enable persistent connections between drweb-icapd and Squid, which improves performance: icap_persistent_connections on
|