User Guide
Table Of Contents
- KASPERSKY ANTI-VIRUS FOR PROXY SERVER
- OPERATION ALGORITHM AND TYPICAL DEPLOYMENT SCENARIOS
- INSTALLING THE APPLICATION
- USING KASPERSKY ANTI-VIRUS
- ADDITIONAL SETTINGS OF KASPERSKY ANTI-VIRUS
- Creating groups
- Anti-virus scan settings
- The choice of actions over scanned objects
- Administrator notifications
- Operation modes
- Modes of interaction with proxy via ICAP
- Application statistics logging
- Application reporting parameters
- Memory dump creation for detection of errors
- Work with Internet broadcasting stations
- UNINSTALLING THE APPLICATION
- APPLICATION REFERENCE
- KASPERSKY LAB
- LICENSE AGREEMENT

Appendix A 53
The [icapserver.actions] section contains the settings for actions over scanned
objects for the default group:
CuredAction – action over disinfected objects.
InfectedAction – action over infected objects.
SuspiciousAction – action over suspicious objects.
WarningAction – action over an object resembling a known virus.
ErrorAction – action over an object, which has caused a scanning error.
ProtectedAction – action over password-protected objects.
CorruptedAction – action over damaged objects.
LicenseErrorAction – action over scanned objects if the application has
failed to load the license key information.
BasesErrorAction – action performed over objects in cases, when the
application fails to load the anti-virus databases.
The [icapserver.notify] section contains notification parameters for the default
group:
NotifyTemplateDir – directory where the notification templates are stored.
NotifyScript – script used by the application to notify the administrator
about objects prohibited for transfer through the proxy server.
The [updater.path] section contains the paths to directories and files necessary
for the functioning of the keepup2date component:
BackUpPath – path to the directory where an archive of the anti-virus databases
is preserved during their update. This is a mandatory parameter.
UploadPatchPath – path to the directory containing application patches.
PidFile – path to PID file. It is used to prevent simultaneous launch of several
instances of the keepup2date component. If the parameter is missing, the
PID file will not be created. Consequently, no checks for other running
instances of the component will be performed.
AVBasesTestPath – full path to the avbasestest utility validating the anti-virus
databases. The application uses it immediately after downloading of
updates. Only if the received updates are intact, they will be copied from a
temporary folder to the storage directory. If this parameter is not specified,
then during an update the updater will output to the console and log file a
message informing about inability to check the downloaded anti-virus
databases; the updates will be installed then without further validation.










