Apache HTTP Proxy
Apache HTTP Proxy is a proxy service that can be used to distribute updates to client computers.
To install Apache HTTP Proxy, read the instructions for Windows, Linux, or Virtual Appliance.
Apache HTTP Proxy functions
Function |
Proxy solution that provides this function |
---|---|
Caching of downloads and updates |
Apache HTTP Proxy or other proxy solution |
Caching of ESET LiveGuard Advanced results |
Only configured Apache HTTP Proxy |
Replication ESET Management Agents' communication with ESET PROTECT Server |
Apache HTTP Proxy or other proxy solution |
Caching function
Apache HTTP Proxy downloads and caches:
•ESET module updates
•Installation packages from repository servers
•Product component updates
Cached data is distributed to endpoint clients on your network. Caching can significantly decrease internet traffic on your network.
In contrast to the Mirror Tool, which downloads all available data on the ESET update servers, Apache HTTP Proxy reduces the network load by only downloading the data requested by ESET PROTECT components or ESET endpoint products. If an endpoint client requests an update, Apache HTTP Proxy downloads it from the ESET update servers, saves the update to its cache directory and then serves it to the individual endpoint client. If another endpoint client requests the same update, Apache HTTP Proxy serves the download to the client directly from its cache, so there is no additional download from ESET update servers.
Caching for ESET Endpoint product
Caching settings of ESET Management Agent and Endpoint are not identical. ESET Management Agent can manage settings for ESET security products at client devices. You can set up proxy for ESET Endpoint Security:
•locally from GUI
•from ESET PROTECT Web Console, using a policy (the recommended way to manage client devices settings).
Caching results from ESET LiveGuard Advanced
Apache HTTP Proxy can also cache results provided by ESET LiveGuard Advanced. Caching requires specific configuration which is included in the Apache HTTP Proxy distributed by ESET. It is recommended to use caching with ESET LiveGuard Advanced if possible. See the service's documentation for more details.
Using Apache as HTTP Proxy for Agent - Server communication
When correctly configured, Apache HTTP Proxy can be used to collect and forward data from ESET PROTECT components in a remote location. One proxy solution can be used for caching updates (Apache HTTP Proxy is recommended) and another proxy for Agent - Server communication. You can use Apache HTTP Proxy for both functions at the same time, but it is not recommended for networks with more than 10,000 client machines per proxy machine. In enterprise environments (more than 1,000 managed computers), we recommend that you use a dedicated Apache HTTP Proxy server.
Read more about the Proxy function.
How to set up the HTTP Proxy
To use the proxy, HTTP Proxy hostname must be set up in the Agent policy (Advanced settings > HTTP Proxy). You can use different proxies for caching and forwarding; see the policy settings below:
•Global Proxy - you will use a single proxy solution for both caching downloads and for forwarding Agent communication.
•Different Proxy Per Service - you will use separate proxy solutions for caching and for forwarding communication.
Apache HTTP Proxy in the infrastructure
The following diagram illustrates a proxy server (Apache HTTP Proxy) that is being used to distribute ESET cloud traffic to all ESET PROTECT components and ESET endpoint products.
You can use a proxy chain to add another proxy service to a remote location. Note that ESET PROTECT does not support proxy chaining when the proxies require authentication. You can use your own transparent web proxy solution, however that may require additional configuration beyond what is mentioned here. |