Lanny Baron wrote: > Then what's the biggy to just do 2 vhosts?? One regular and one https. For then, one would violate the Prime Directive and have to Define the Same Thing Twice and thou should not goest that way for it is a way of pain and much suffering and leads inevitably to you changing one and not the other and getting all in a mess and then some snotty consultant spots it and has you arrested for violating the Prime Directive and you end up writing VBscript where nobody cares about these things... ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
- Re: Serving HTTP & HTTPS in one VHost... R. DuFresne
- Re: Serving HTTP & HTTPS in one VHost-Conf... Thomas Binder
- Re: Serving HTTP & HTTPS in one VHost-Conf... Owen Boyle
- Re: Serving HTTP & HTTPS in one VHost-Conf... Mads Toftum
- Re: Serving HTTP & HTTPS in one VHost-Conf... Lanny Baron
- Re: Serving HTTP & HTTPS in one VHost-Conf... Owen Boyle
- Re: Serving HTTP & HTTPS in one VHost-Conf... Alex Pircher
- Re: Serving HTTP & HTTPS in one VHost-Conf... Lanny Baron
- Re: Serving HTTP & HTTPS in one VHost-Conf... Owen Boyle
- Re: Serving HTTP & HTTPS in one VHost... Merton Campbell Crockett
- RE: Serving HTTP & HTTPS in one VHost-Conf... John . Airey
- Re: Serving HTTP & HTTPS in one VHost-Conf... Charles & Kathryn Brown
- Re: Serving HTTP & HTTPS in one VHost... Alex Pircher
