7 Jan
2022
7 Jan
'22
8:04 a.m.
Mark Sapiro writes:
On 1/6/22 6:28 PM, Stephen J. Turnbull wrote:
In my Debian configuration [mod_proxy_http.conf] is needed because it contains the necessary directives to enable proxying.
Actually though, I think that's enabled as part of proxy.
The Apache documentation strongly implies that this needs to be explicitly enabled by the admin:
The forward proxy is activated using the ProxyRequests
directive. Because forward proxies allow clients to access
arbitrary sites through your server and to hide their true origin,
it is essential that you secure your server so that only
authorized clients can access the proxy before activating a
forward proxy.By contrast for a reverse proxy:
A reverse proxy is activated using the ProxyPass directive or the
[P] flag to the RewriteRule directive. It is not necessary to turn
ProxyRequests on in order to configure a reverse proxy.Both are from https://httpd.apache.org/docs/2.4/mod/mod_proxy.html.
However, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
I now suspect the real issue is there's no wsgi server listening on port 8000.
Could be. Apache docs notwithstanding, I'm happy to trust your intuition, and that would make things simple for the OP. :-)
Steve