Dr.Web HTTPD

Top  Previous  Next

Dr.Web HTTPD provides infrastructure for local and remote interaction with Dr.Web for UNIX File Servers via HTTP (for example, via a web browser). The component provides two interfaces: an interface to manage the product (in addition to installing the Dr.Web HTTPD, a separate package must also be installed containing the files of the web interface for managing the product via a web browser) and a service interface used by the Dr.Web Link Checker component, which is an extension for Mozilla Firefox and Google Chrome browsers (installed separately).

Besides managing Dr.Web for UNIX File Servers through the product’s web interface, it is also possible to use the command interface (HTTP API) of Dr.Web HTTPD directly to interact with the components of Dr.Web for UNIX File Servers via HTTPS. This capability allows you to create your own interface to manage Dr.Web for UNIX File Servers.

To use a secure HTTPS connection it is required to provide an appropriate SSL server certificate and private key for Dr.Web HTTPD. By default, an SSL server certificate and an SSL private key are generated for Dr.Web HTTPD automatically during the installation procedure, but, if necessary, you can generate your own certificate and key. If you need to generate SSL keys and certificates, you can use the openssl utility. An example of how to use the openssl utility to generate a certificate and a private key is given in the section Appendix E. Generating SSL certificates.

 

Details:

Operating Principles

Command Line Arguments

Configuration Parameters