HUm, try checking if you've loaded mod_ssl, and defined the ports that
apache should listen to (default is only port 80, https usually
connects on 443).
Also you will have to split your virtualhost in a secure and a
non-secure site (can't think of another way of making this work), you
will also have to create certificate-file's using openssl.
What I usually do is have a non-secure site show the first page of a
site and then redirect the next pages to the secure site.
I'm also a bit puzzled by the mod_proxy directive in a virtualhost
directive, what is the intended result of that??
> I think, if i remember correctly, the problem with https is that you
> can't run multiple https servers on a single machine using name based
> virtual hosts. I think this has to do with the way that https works.
> It *should* work for http requests. I think there's something on the
> modssl.org website that covers this issue. I'm not sure if this
> answered your question, i'm pretty green on proxies.
> > I am somewhat green in working with the Apache Server. Here are the
> > directives I am using for a reverse proxy implementation. This will
> > not work for an HTTPS request. How can I modify to dynamically work
> > with HTTP or HTTPS requests?
> > <VirtualHost 172.20.64.90>
> > ServerName www.sam-art.org
> > ErrorDocument 502 /error/maintenance.html
> > DocumentRoot "c:/program files/apache group/apache/htdocs/sam-art"
> > CustomLog logs/sam-art.access.log common
> > ErrorLog logs/sam-art.error.log
> > <IfModule mod_proxy.c>
> > CacheRoot "C:/Program Files/Apache Group/Apache/proxy/sam-art"
> > NoCache *
> > Redirect /index.html http://usa.samsonite.com/lansaimg/samart/
> > ProxyRequests On
> > ProxyPassReverse /lansaimg/samart http://usa.samsonite.com/lansaimg/samart/
> > ProxyPass /lansaimg/samart http://usa.samsonite.com/lansaimg/samart/
> > </IfModule>
> > </VirtualHost>
> > Please help...Dan