11.3 HTTP and FTP scanning
Figure 11.8 Definition of an HTTP/FTP scanning rule
—this option filters out certain filenames (not entire URLs) transmitted by FTP or HTTP (e.g. *.exe, *.zip, etc.).
If only an asterisk is used for the specification, the rule will apply to any file transmitted by HTTP or FTP.
The other two conditions can be applied only to HTTP:
•MIME type
— MIME types can be specified either by complete expressions (e.g. image/jpeg) or using a wildcard matching (e.g. application/*).
•URL — URL of the object (e.g. www.kerio.com/img/logo.gif), a string speci- fied by a wildcard matching (e.g. *.exe) or a server name (e.g. www.kerio.com). Server names represent any URL at a corresponding server (www.kerio.com/*).
If a MIME type or a URL is specified only by an asterisk, the rule will apply to any HTTP object.
Action
Settings in this section define whether or not the object will be scanned.
If the Do not scan alternative is selected, antivirus control will not apply to trans- mission of this object.
The new rule will be added after the rule which had been selected before Add was clicked. You can use the arrow buttons on the right to move the rule within the list.
Checking the box next to the rule can be used to disable the rule. Rules can be disabled temporarily so that it is not necessary to remove rules and create identical ones later.
Note: If the object does not match with any rule, it will be scanned automatically. If only selected object types are to be scanned, a rule disabling scanning of any URL or MIME
