Reverse Proxy with SSL

[mrudmann]

Hi all,
Does anyone out there have a procedure for configuring a SSL reverse proxy in apache for alfresco?

My vitual host in httpd.conf looks like this:

<VirtualHost *:443>
   ServerName myservername
   ProxyRequests Off
   ProxyPass         / http://192.168.1.100:8082/
   ProxyPassReverse  / http://192.168.1.100:8082/
   SSLEngine On
   SSLCertificateFile /usr/share/ssl/certs/myapache.pem
</VirtualHost>


I was hoping that this configuration would have directed inbond port 443 (ssl) traffic and proxy it to 192.168.1.100 on port 8082 (where I have my alfresco proxy server running).

The symptoms of the above config are that when I web to https://myservername/alfresco I get a "page cannot be found" error from internet explorer.  If I just web to https://myservername I get the fedora core test page   I think I am turned around a little.

Can anyone help out?

Thanks!!
-Matt

[mrudmann]

Ok guys an update.

I just ripped out  of my httpd.conf that configuration of the virtual host and slapped it into the ssl.conf for apache.  The results are much different.

When I web to https://myservername/alfresco, I get directed to alfresco seemingly OK.

Now here is what I actually want to accomplish…

I would like to take advantage of caching and https.  Is this possible?  I was hoping I could use the proxy alfresco from the server.xml which runs on port 8082 and somehow have this run under/within/inside, etc. ssl.

Does that make sense?  Is it possible?  If so, any ideas on the matter are greatly appreciated!

Thanks!
-matt

[mrudmann]

I should have mentioned that when I do get seemingly redirected to alfresco now, I no longer am running in a secured environment.

Again, any help is appreciated.

-Matt

[mavo]

the same problem for me; it's the footer that has hard-coded http://-links in it and prevents the browser to think all stuff is secure …

[mrudmann]

mavo,

If you search for my postes elsewhere on these forums, you should find where I was able to get the site running under SSL.

What would be really slick is to run only the log in page under ssl so there is not as much overhead.  I understand there is a way to do this, but I did not have time to pursue this ideal (for me) solution.

Again, look for my posts and that should lead you to the ssl solution.