NCSA httpd: BindAddress and VirtualHosting

NCSA httpd: BindAddress and VirtualHosting

Post by Brett Bendickso » Thu, 31 Oct 1996 04:00:00



Is it possible to not bind to * and still use virtual
hosting?

A user wants Microsoft's Frontpage extensions installed.
They only support up to 1.5, not 1.5.2. For various reasons
I do _not_ want to back up versions. MS's solution suggests
upgrading to Apache, which isn't very feasible right now. So my
solution, which is theoretically possible, is to put up another
server, Apache, and have it bind to a different ip on port
80.

Apache is setup correctly to bind only to 128.196.139.69.

The end of my httpd.conf file is:

#BindAddress 128.196.

<VirtualHost 128.196.139.65>
ServerName w3.arizona.edu
ResourceConfig conf/srm.conf
</VirtualHost>

<VirtualHost 128.196.139.66>
ServerName wildcat.arizona.edu
ResourceConfig conf/wildcat_srm.conf
TransferLog logs/wildcat_access_log
</VirtualHost>

<VirtualHost 128.196.139.67>
ServerName www.openair.org
ResourceConfig conf/openair_srm.conf
TransferLog logs/openair_access_log

</VirtualHost>

<VirtualHost 128.196.139.68>
ServerName www.cesl.arizona.edu
ResourceConfig conf/cesl_srm.conf
TransferLog logs/access_log

</VirtualHost>

However, the server still appears to claim all IP addresses,
because on starting Apache I get

bind: Address already in use
httpd: could not bind to address 128.196.139.69 port 80

Any suggestions to work this out would be greatly
appreciated.

Thanks,
Brett

--
Brett Bendickson - UAInfo Web Team