Re: NameVirtualHost nat
Hi! Lars H. Beuse [EMAIL PROTECTED] 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 | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * If it wasn't for C, we'd be using BASI, PASAL and OBOL! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NameVirtualHost nat
On Tue, 12 Oct 2004 21:26:55 +0300, Toomas Aas [EMAIL PROTECTED] wrote: Hi! Lars H. Beuse [EMAIL PROTECTED] 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. Indeed. This sounds like something isn't wuite right with the Apache setup. Lars, have you tried accessing the webserver from your private network, localhost, with/without the firewall enabled. Does that make any difference or do you get the same result each time? You could also try setting LogLevel debug in httpd.conf and see what errors (if any) you are getting. It's probably best though if you post the VirtualHost section of your httpd.conf. Hope this helps. David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NameVirtualHost nat
On Tuesday 12 October 2004 21:53, David Jenkins wrote: On Tue, 12 Oct 2004 21:26:55 +0300, Toomas Aas [EMAIL PROTECTED] wrote: Hi! Lars H. Beuse [EMAIL PROTECTED] 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. [...] Jepp, that's why i'am a bit confused. Cause unfiltered ApacheVirtualHosts i run a few. So i think i solved that issue: That was my Virtual Host Container before it works: NameVirtualHost www.domain.org:80 VirtualHost www.domain.org:80 blablabla /Virtual The Container that works: NameVirtualHost 192.168.2.5:80 VirtualHost 192.168.2.5:80 blablabla /Virtual Thanx, for youre reply. But why is that? I'm not really shure. So i will go deeper in that. Ciao Lars ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NameVirtualHost nat
Hi, 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. Greetings Lars H. Beuse ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
