Mailing List Archive

> From: Randy Terbush <randy@hyperreal.com>
> Date: Wed, 3 May 1995 11:10:34 -0700 (PDT)
>
> Sorry for the lack of docs on this. Coming RSN... :-)
>
> Actually, I've seen the two paragraphs below from Randy often enough
> that I've thought of just installing them on hyperreal as placeholders
> until the real virtual_host docs are available...

I'll do this tonight. I have planned to do the same but have been
short of time. I will also include the VIF patch that I mention.

-Randy

From: Randy Terbush <randy@hyperreal.com>
Date: Wed, 3 May 1995 11:10:34 -0700 (PDT)

Sorry for the lack of docs on this. Coming RSN... :-)

Actually, I've seen the two paragraphs below from Randy often enough
that I've thought of just installing them on hyperreal as placeholders
until the real virtual_host docs are available...

Firstly, you must configure your server machine to be able to
accept IP packets for multiple addresses either through the
'ifconfig alias' flag, or through kernel changes to support
VIF. There are some pages for SunOS floating around the net
for VIF support.

Next, add the following entry to httpd.conf. It should "just work".

# Virtual Host Config
<VirtualHost www.foo.com>
ServerAdmin webmaster@www.foo.com
DocumentRoot /www/docs/foo.com
ServerName www.foo.com
ErrorLog logs/foo.com-error_log
TransferLog logs/foo.com-access_log
</VirtualHost>


rst

This is in.

Being the terse individual that I am, I cannot really find
much more to say about this feature beyond what I have
entered. It just works.

Hi, everybody!
> Firstly, you must configure your server machine to be able to
> accept IP packets for multiple addresses either through the
> 'ifconfig alias' flag,
This works for Solaris 2.x only, doesn't it?
> or through kernel changes to support
> VIF. There are some pages for SunOS floating around the net
> for VIF support.
I have such page by my own. Instructions provided DO NOT require kernel
changes! Try out http://fy.chalmers.se/~appro/VIF.html. It makes
"VIFing" as easy as breath...

Andy.

> Hi, everybody!
> > Firstly, you must configure your server machine to be able to
> > accept IP packets for multiple addresses either through the
> > 'ifconfig alias' flag,
> This works for Solaris 2.x only, doesn't it?

No. Most modern 'ifconfig's can do this. ie BSD/OS, NetBSD, FreeBSD,
I suspect any SVR4, others?

> > or through kernel changes to support
> > VIF. There are some pages for SunOS floating around the net
> > for VIF support.
> I have such page by my own. Instructions provided DO NOT require kernel
> changes! Try out http://fy.chalmers.se/~appro/VIF.html. It makes
> "VIFing" as easy as breath...

I will check this out. I put a link to the VIF info I had that is
now at http://www.apache.org/apache/docs/vif.info.

> >Being the terse individual that I am, I cannot really find
> >much more to say about this feature beyond what I have
> >entered. It just works.
>
> Could you document the BindAddress config option as well please?
> And maybe a short section on when to use BindAddress or
> VirtualHost... (For example, if you want different srm.confs for your
> domains, then using BindAddress and multiple daemons would be better.)

I have not used these features. Perhaps you would be better
qualified to add this information.

> > > Firstly, you must configure your server machine to be able to
> > > accept IP packets for multiple addresses either through the
> > > 'ifconfig alias' flag,
> > This works for Solaris 2.x only, doesn't it?
>
> No. Most modern 'ifconfig's can do this. ie BSD/OS, NetBSD, FreeBSD,
> I suspect any SVR4, others?
>
Original question was very specific and it was about SunOS 4.x. When I
wrote "Solaris" I ment whole SunOS family...

Andy.

> Can someone please do the following:
> 1. Change the link in /apache/docs/index.html `Multi-homed host support'
> to point at this file instead of httpd.conf.html#virtualhost

done

> 2. Update /apache/docs/httpd.conf.html to include:

done

> 3. Put links to virtual-host.html in any place it is needed. (such as
> the VirtualHost descrption in httpd.conf.html

done.



-=-=
BTW, the latest vote scores are now available at
http://hyperreal.com/httpd/cgi-bin/vote.cgi


robh

>Being the terse individual that I am, I cannot really find
>much more to say about this feature beyond what I have
>entered. It just works.

Could you document the BindAddress config option as well please?
And maybe a short section on when to use BindAddress or
VirtualHost... (For example, if you want different srm.confs for your
domains, then using BindAddress and multiple daemons would be better.)

David.

(re BindAddress documentation)
>I have not used these features. Perhaps you would be better
>qualified to add this information.

I haven't used it either...
Unfortunately the transatlantic link is now so bad that I am simply wasting
my time attempting to do anything on hyperreal. I have previously resorted
to ftping the entire apache docs to my machine, editing them here, and then
copying them back. Rather error prone, though.

So I my email some documentation to the list for someone else to put on
hyperreal.

David.

I've uploaded some more virtual host documentation to hyperreal.
(/apache/docs/virtual-host.html)

Can someone please do the following:
1. Change the link in /apache/docs/index.html `Multi-homed host support'
to point at this file instead of httpd.conf.html#virtualhost
2. Update /apache/docs/httpd.conf.html to include:

<LI><A HREF="#bind">BindAddress</A><IMG SRC="images/new.gif" ALT="NEW"></B>

In the list of options (after `Port'), and add


<H1><A name="bind">BindAddress</A></H1>
<P>Options:
<ol><li>*
<li>&lt;An IP address&gt;
<li>&lt;A fully qualified internet domain name&gt;
</ol>
<P>A unix http server can either listen on for connections to every
IP address of the server machine, or just one IP address of the server
machine.
<p>If the value is "*", then the server will listen for connections on
every IP address, otherwise it will only listen on the IP address
specified. The default is "*".
<P>This option can be used to support <A HREF="virtual-host.html">virtual
hosts</A>.

<HR>

to the descriptions (after Port)

3. Put links to virtual-host.html in any place it is needed. (such as
the VirtualHost descrption in httpd.conf.html

David.