Host a Website and a Private Forward Proxy on One Apache Server

Separate the listener and authorization for a private Apache forward proxy from an existing public website or reverse mapping.

On an existing Apache host, a private forward entrance can use a separate loopback listener:

ProxyRequests Off
Listen 127.0.0.1:3128

<VirtualHost 127.0.0.1:3128>
    ProxyRequests On
    <Proxy "*">
        Require local
    </Proxy>
</VirtualHost>

Merge this with the current configuration; do not declare the same listener twice. Load the required proxy protocol modules. HTTPS destinations through CONNECT additionally require mod_proxy_connect and the intended destination-port policy.

The public virtual host can keep its ProxyPass mappings while forward proxying remains off. ProxyPass maps a local URL space to a backend. ProxyRequests controls clients requesting other destinations; turning it off does not disable reverse mappings.

The excerpt admits local clients or an explicitly arranged local transport endpoint. For LAN use, select an assigned listener address and matching source/authentication rules. Put those permissions on the proxy entrance rather than the public site's document directory.

Review the selected virtual host and inherited directives for every active listener. A global ProxyRequests On can enable the role beyond the intended private entrance. A forward client supplies its destination, so there is no need to create a local mapping for every website it may request.

Artiglyn mynjee