To follow up on this, if the port forwarding of port 80 does not just
forward and you lose the domain requested (I doubt it since it's part of
the http protocol, then you still may have an option. I think you could
then setup virtual hosts on apache on the firewall, and have each of those
use mod_proxy to send the requests to the internal apache server using
different ports for each domain.
I'd try setting up the virtual domains on the internal apache server first
though.
charles
On Thu, 13 Jan 2000, Hossein S. Zadeh wrote:
> On Wed, 12 Jan 2000, Perry Blalock wrote:
>
> > What I'd like to do, but can't seem to visualize at the moment, is to
> > setup multiple domains (inside private), and virtual hosts on apache,
> > and access them all by name, www.this.xxx and www.that.xxx, via the
> > single public ip address. The bottom line is that I want to hosts
> > multiple (free) websites (supporting php and mysql), control the
> > domains for those sites via my own primary DNS, but I only have one
> > public ip address to use.
>
>
> Virtual hosting on a single subnet is by apache "seeing" what the
> requested name was/is. I don't know the exact details of how port
> forwarding is implemented. If your apache "sees" the original request,
> then you're home free; otherwise you're out of luck.
>
> If I were you, I'd check apache logs to see if visits "appear" to be
> coming from your firewall, or from the original requester.
>
> In other words, if port forwarding is done the same as masqurading, then
> you cannot have virtual hosting on a single IP; however if it does "just"
> port forwarding, then you merely need to setup apache for the virtual
> domains, setup the domains' delegations (so people can find you), and away
> you go....
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
