Thanks again. Reply below.
> > > > I must have misunderstood something in the docs. The
> > following is not
> > > > working as I expect it to.
> > > >
> > > > In httpd.conf:
> > > >
> > > > NameVirtualHost *:80
> > > > Include conf/otherdomain.conf
> > > > Include conf/mydomain.conf
> > > >
Thank you for the suggestion. Reply inline below.
> > I must have misunderstood something in the docs. The following is not
> > working as I expect it to.
> >
> > In httpd.conf:
> >
> > NameVirtualHost *:80
> > Include conf/otherdomain.conf
> > Include conf/mydomain.conf
> >
> >
> > In mydom
Hello!
I must have misunderstood something in the docs. The following is not
working as I expect it to.
In httpd.conf:
NameVirtualHost *:80
Include conf/otherdomain.conf
Include conf/mydomain.conf
In mydomain.conf:
ServerName www.mydomain.com
ServerAlias mydomain.com
DocumentRoot /var
> > What seems strange to me is that the proxy host requires
> > a certificate just to tunnel a session to an https backend
> > system... This seems like quite a lot of overhead for
> > nothing...
> well, that is is because it is not just a tunnel. :-)
> If you want just that, then you could use
>> I am having trouble getting my reverse proxy to work with SSL.
>
> Do you want the reverse proxy to be https-enabled, or do you
> want to reverse-proxy to a https-host?
>
> To RP to a https-backend system you need 'SSLProxyEngine on'.
Ah!
That's the little detail I was missing. :-)
Thank
Isha, thank you! Comments inline.
> > I am having trouble getting my reverse proxy to > work with SSL.
> RequestHeader set Front-End-Https "On"
That did something... But now I get a 403 error and a message in my
logs (on the
proxy server) saying:
[warn] proxy: No protocol handler was valid for
Hello!
I am having trouble getting my reverse proxy to work with SSL. Perhaps I
have misunderstood the documentation...
Reverse proxying is working fine for HTTP connections.
The only message I notice in my log files is "Invalid method in request
\x16\x03".
The following is the relevant s
