Operating Principles

Dr.Web HTTPD is a web server for managing the operation of Dr.Web for UNIX File Servers. With Dr.Web HTTPD, it is possible not to use external web servers (for example, Apache HTTP Server or Nginx) and management services like Webmin. Moreover, the component can function simultaneously with such servers and services on the same host and not impede their operation at that.

The Dr.Web HTTPD server processes requests received via HTTP and HTTPS protocols to the sockets specified in the settings. For this reason, the server does not have any conflicts with web servers when they operate on the same host. The operation scheme is shown in the figure below.

Figure 21. Diagram of the components’ operation

HTTPS is used for product management; and HTTP, for processing requests from Dr.Web Link Checker—a web browser extension—(it is installed to the browser separately).

The Dr.Web HTTPD component issues commands to the Dr.Web for UNIX File Servers Dr.Web ConfigD configuration daemon, as well as to the Dr.Web File Checker component for file checking, and to SpIDer Guard for NSS monitor. These commands are based on those that were received through the provided HTTP API (including those that were made via the management web interface or those made as requests from the Dr.Web Link Checker browser extension).

If the management web interface of Dr.Web for UNIX File Servers, which uses Dr.Web HTTPD, is included in the product, it is described in the corresponding section.

If the Dr.Web’s management web interface is not included in the product, it is possible to connect any external management interface to the product. For interaction with the product’s components, this interface should use the HTTP API provided by Dr.Web HTTPD (not described in this user manual).