[EMAIL PROTECTED] wrote: > > RedirectMatch (.*) https://d.com$1 > > > > Won't this create an infinate loop? > I could be wrong, but I think RedirectMatch will pick up the hit via http or https, >and attempt to send the user to https://d.com$1 even if the user came via https in >the first place. >
It depends on the "context" - i.e. where you put the directive in the httpd.conf file. If you put it outside of any virtualhost container it will have "server-config" context which means it will apply globally to all VHs. Then you will have trouble... However, if you have virtualhosts defined and you put the directive inside a VH container, it will have "virtualhost" context which means that it will only apply to that VH. Since you are using VHs, you must put the directive inside the plain HTTP VH for "d.com". Then it will only apply to HTTP requests to d.com. > mod_rewrite seems to be the only alternative I've seen so far. If I'm wrong, let me >know... mod_rewrite is great and I'm a big fan, but it is a sledge-hammer to crack a nut in this instance. Rgds, Owen Boyle. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
