Did you try using SSLProxyEngine On ? Normally, you do not need to use SSL when proxying, as SSL is used to secure contents, and if you install SSL certificate on Apache which is proxing you do not need to have SSL on backend servers
On Wed, Sep 19, 2012 at 5:40 PM, Vivek Nambiar <[email protected]>wrote: > Hi Jeremy, > > If you add a / infront of the SSL URL,then does it work? > > Thanks > > On Wed, Sep 19, 2012 at 11:43 AM, Jeremy T <[email protected]> wrote: > >> Hi All, >> >> I had a question about Apache with SSL. >> Basically came across this issue when configuring a reverse proxy with >> Apache. >> >> Do you know if there is some limitation on the number of ProxyPass and >> ProxPassReverse entries that you can do when it comes to an SSL virtual >> host? >> >> *Consider the following scenario:* >> 1. I have a website called http://public1 and have a public SSL cert for >> that site. >> 2. I have two internal servers with different urls containing self signed >> SSL certs for both of them. >> 3. Internal urls are https://internal1:81 and https://internal2:82 >> 4. I would like to have https://public1 proxy to https://internal1:81and >> https://public1/demo proxy to https://internal2:82 >> >> >> *Configuration: >> * >> Proxypass /demo https://internal2:82 >> >> ProxyPassReverse /demo https://internal2:82 >> >> ProxyPass / https://internal1:81 >> >> ProxyPassReverse / https://internal1:81 >> >> >> >> *The problem:* >> It seems that the /demo entries do not work (the first two entries). >> However these rules work for non SSL virtual hosts. The problem is when I >> work with SSL virtual hosts. >> >> ANY help / tips or limitations with the above would be helpful. >> >> Thank you >> Jeremy >> >> >> >
