Date: Thu, 21 Sep 2000 12:15:21 -0400 From: Jon Parise <jon@csh.rit.edu> To: freebsd-isp@freebsd.org Subject: Re: named virtual hosts Message-ID: <20000921121520.B20273@csh.rit.edu> In-Reply-To: <20000921111406.A11386@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Thu, Sep 21, 2000 at 11:14:06AM %2B0200 References: <20000912184042.D55208@bsd.planetwe.com> <20000916041934.B769@hand.dotat.at> <20000921111406.A11386@mithrandr.moria.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 21, 2000 at 11:14:06AM +0200, Neil Blakey-Milner wrote: > > >NameVirtualHost 192.168.21.21 > > ><VirtualHost 192.168.21.21> > > ></VirtualHost> > > ><IfDefine SSL> > > > <VirtualHost 192.168.21.21:443> > > > </VirtualHost> > > ></IfDefine> > > > > You can't do SSL with name-based virtual hosts. > > Why not? The SSL layer wraps around the HTTP protocol. The Host: header that makes NameVirtualHost work is part of the HTTP protocol (HTTP 1.1?), so the SSL code never gets to the NameVirtualHost stuff in time. In a nutshell, in order to use SSL-enabled virtual hosts, you'll have to assign each virtual host its own IP address and use Apache's IP-based virtual hosting system. -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000921121520.B20273>