Date: Tue, 12 Oct 2004 21:26:55 +0300 From: "Toomas Aas" <toomas.aas@raad.tartu.ee> To: "Lars H. Beuse" <bsd@dokfilm.org>, questions@freebsd.org Subject: Re: NameVirtualHost nat Message-ID: <200410121827.i9CIRJ3m010356@lv.raad.tartu.ee> In-Reply-To: <200410120127.42002.bsd@dokfilm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! "Lars H. Beuse" <bsd@dokfilm.org> wrote: > i want some apache NameVirtualHost behind a Paketfilter based on ipf, placed > in two subnets. This router has two Cards one in the private net, one in the > public. So far i just forward port 80 and 443 into my private net > 192.168.2.0, but every request ends up on apaches rootlevel, NameVirtualHost > directive is useless. So, how to forward http(s):// requests through the > Paketfilter matching the right VirtualHost? Maybe i've thought in a wrong > direction, so far. Just some little hints should be enough. I can't be 100% sure because I haven't done this kind of thing myself, but I don't see why port forwarding should interfere with Apache's name-based virtual hosting. After all, they operate on different layers of the OSI model: port forwarding is purely TCP business while VirtualHosts are HTTP. I can tell you, though, that name-based virtual hosting can't be used with https. IIRC this is written in the FAQ on the mod_ssl webpage. -- Toomas Aas | toomas.aas@raad.tartu.ee | http://www.raad.tartu.ee/~toomas/ * If it wasn't for C, we'd be using BASI, PASAL and OBOL!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410121827.i9CIRJ3m010356>