--- [EMAIL PROTECTED] wrote:
>Can you turn on "LogLevel Debug" and post some lines out of it.
>If occur, Lines around "proxy: HTTPS: declining URL" or "proxy: HTTP:
>serving URL"
Ok, I tried that, but nothing like HTTPS in the logs. As I said, I suspect that
the problem is in rewriting replies p
> Only to make a ProxyPassReverse is not enough to make https
> Do you have in your httpd.conf at least Lines like this ?
> SSLEngine On
> SSLProxyEngine On
> Listen fe:443
Yes, I do have lines like this. However, based on the reponses from the Apache
proxy, the browser never initiates a https ses
--- [EMAIL PROTECTED] wrote:
> Where in your config should come the https from ?
>
> If you want a secure communication to the backend than make a virtual host on
> Port 80 for the frontend, rewrite than all incoming requests from the second
> virtual host which is listening on Port 443 of your f
I am struggling to set up a reverse proxy, and for some reason, just can't get
it right.
I have a public server (will call it "frontend") to access a private one
("backend"). The "backend" sends a couple of redirects, which seem to confuse
the ProxyPassReverse, so eventually my browser ends up qu
