I don't use owa, but I have similar configration for https. in my case we use internal dns and external dns, so I can use the same hostname in internal and external dns but for different ip address. in internal dns, the hostname point to the real webserver and in external dns it points to reverse proxy (revproxy use internal dns). so for owa connection , my configuration would look like: User in the internet -> https://owa.mydomain.com/ -> https://owa.mydomain.com/
<VirtualHost *:443> ServerName owa.mydomain.com SSLProxyEngine on ProxyPass / https://owa.mydomain.com/ ProxyPassReverse / https://owa.mydomain.com/ </VirtualHost> <VirtualHost *:80> ServerName owa.mydomain.com RewriteRule ^/(.*) https://owa.mydomain.com/$1 </VirtualHost> the virtual host on port 80 is needed to redirect any http connection to https in case the real webserver sent a url with http like in your case with <BASE href="http://...";>. cahya. On Mon, Dec 01, 2003 at 11:43:03AM +0200, Haim Marko wrote: > User in the internet -> https://owa.domain.com/ -> > http://owainternal.internaldomain.com/exchange/ > > On the apache's httpd.conf I have the folowing configuration: > > <VirtualHost *:443> > > ServerName owa.domain.com > > ProxyPass / http://owainternal.internaldomain.com/exchange/ > > ProxyPassReverse / http://owainternal.internaldomain.com/exchange/ > > </VirtualHost> > > In the 1st page I'm getting contains the following tag: > > <BASE href="http://owainternal.internaldomain.com/exchange/Username/";> > > Meaning that all relative links on the page will be changed to point to the > internal server > > which is not accessible from the internet. Setting up the same name for both > external and > internal servers doesn't solve the problem because the BASE href points to > http and not https. > > Is there a way to search and replace pages going back to the user (like > mod_rewrite in the > opposite Direction) ? Or other solution ? > > 10x > > Best Regards, > Haim Marko, ITI Comverse > > > >
