Brad brings up an important point.   I was never successful in forwarding port 80 traffic from the reverse proxy to the virtual host listening on 443.  For example: A rev proxy listening on port 80 forwarding back to a virtual host on port 443.  The reverse proxy listens on port 80 and 443 for all the traffic coming in from the external IP and natted back to the reverse proxy.

Here is why:  The originating client will request port 443 when an https URL is used.  If you have a reverse proxy listening on 80, it won't handle that traffic.  But, if you do accept https traffic on the reverse proxy, then you need to listen on 443 AND have a certificate for the virtual host BEFORE you can pass traffic back to it.  There are a couple of scenarios where end to end encryption is required:  Https traffic at the reverse proxy is then forwarded to a virtual host that also listens on 443 but I haven't had that requirement and so never configured it.

The issue is that the reverse proxy has to listen on 443 in order to process the https requests.  That is why the virtual hosts listen on 443 and then pass the traffic back to the specific host.

Pete Helgren

On 1/11/2022 9:56 AM, Brad Stone wrote:
Go back and look at Pete's and my examples. The SSL Application names are
in the VirtualHost container for each domain we are forwarding to.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.