Apache Http Proxy

Posted on  by admin

In this post I configure a url redirection from HTTP to HTTPS and viceversa using the Apache modproxy and the ProxyPass directive. I assume an environment consisting of two hosts: a Web Server Apache in front of a Tomcat Applicaton Server.In the following first example the Apache ProxyPass redirects the HTTP requests to the SSL port 8443 of the Tomcat Server.


Apache HTTP Proxy is a proxy service that can be used to distribute updates to client computers. Apache HTTP Proxy performs a similar role to the mirror server feature popular in ERA 5 and earlier.

To install Apache HTTP Proxy, read the instructions for Windows, Linux, or Virtual Appliance.

Apache http proxy redirect

I want to configure my Apache proxy server to redirect certain URLs so that, for example, a web browser HTTP request for www.olddomain.com gets passed to the proxy server which then routes the request to www.newdomain.com which sends a response to the proxy server which then passes it back to the web browser. Use apache as a HTTPS to HTTP Proxy. Ask Question Asked 8 years, 1 month ago. Active 3 years, 6 months ago. Viewed 34k times 10. I'm trying to configure Apache on Centos 6 to proxy and reverse proxy traffic to an http server of a third party provider. Under Apache 1.x, modproxy only supported HTTP/1.0, but from Apache 2.0, it supports HTTP/1.1. This distinction is particularly important in a proxy, because one of the most significant changes between the two protocol versions is that HTTP/1.1 introduces rich new cache control mechanisms.

Apache HTTP Proxy functions


Proxy solution that provides this function

Caching of downloads and updates

Apache HTTP Proxy or other proxy solution

Caching of ESET Dynamic Threat Defense results

Only configured Apache HTTP Proxy

Replication ESET Management Agents' communication with ESMC 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 ESMC 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 ESMC Web Console, using a policy (the recommended way to manage client devices settings)

Caching results from ESET Dynamic Threat Defense

Apache HTTP Proxy can also cache results provided by ESET Dynamic Threat Defense. Caching requires specific configuration which is included in the Apache HTTP Proxy distributed by ESET. It is recommended to use caching with ESET Dynamic Threat Defense 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 ESMC components in a remote location - similarly to the function of ERA 6.x Proxy component. One proxy solution can be used for caching updates (Apache HTTP Proxy is recommended) and another proxy for Agent - Server communication. It is possible to use Apache HTTP Proxy for both functions at the same time, but it is not recommended for networks with more than 1000 client machines per proxy machine.

ERA 6.x Proxy component is not compatible with the ESET Management Agents. Read more about the Proxy function.

Apache Virtualhost Proxypass

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 ESMC components and ESET endpoint products.



You can use a proxy chain to add another proxy service to a remote location. Note that ESMC 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.

Apache Http Proxy Cache Delete


For offline detection engine updates, use the Mirror Tool instead of Apache HTTP Proxy. This tool is available for both platforms (Windows and Linux).

Running several name-based web sites on a single IP address.

Your server has multiple hostnames that resolve to a single address, and you want to respond differently for www.example.com and www.example.org.

Apache Http Proxy Download


Creating virtual host configurations on your Apache server does not magically cause DNS entries to be created for those host names. You must have the names in DNS, resolving to your IP address, or nobody else will be able to see your web site. You can put entries in your hosts file for local testing, but that will work only from the machine with those hosts entries.

The asterisks match all addresses, so the main server serves no requests. Due to the fact that the virtual host with ServerName www.example.com is first in the configuration file, it has the highest priority and can be seen as the default or primary server. That means that if a request is received that does not match one of the specified ServerName directives, it will be served by this first <VirtualHost>.

The above configuration is what you will want to use in almost all name-based virtual hosting situations. The only thing that this configuration will not work for, in fact, is when you are serving different content based on differing IP addresses or ports.


You may replace * with a specific IP address on the system. Such virtual hosts will only be used for HTTP requests received on connection to the specified IP address.

Apache Http Proxy Cache

However, it is additionally useful to use * on systems where the IP address is not predictable - for example if you have a dynamic IP address with your ISP, and you are using some variety of dynamic DNS solution. Since * matches any IP address, this configuration would work without changes whenever your IP address changes.