config/989: 'bindaddress' in a directive block sometimes affects entire server.

[Jeremy Blackman <lo...@maison-otaku.net>]

>Number:         989
>Category:       config
>Synopsis:       'bindaddress' in a <virtualhost> directive block sometimes affects entire server.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Aug 11 12:20:01 1997
>Originator:     loki@maison-otaku.net
>Organization:
apache
>Release:        1.2.1 (and earlier)
>Environment:
Apache 1.2.1 (though I saw the problem with 1.2b7 and 8 also).
Linux 2.0.24 (RedHat 4.0)
>Description:
I have virtual hosts for several of the users on my site; recently I went to change
them over to IP based.

Instead of changing the <virtualhost sitename> to <virtualhost IP> I first
tried adding 'bindaddress' commands into the virtualhost block.  What it did
was only bind the server to the IP address of the last 'bindaddress'.

(e.g. it ONLY listened on the address for 'genesis.maison-otaku.net', 
the final site, when it should have also listened on 
'www.maison-otaku.net' and 'spoof.maison-otaku.net')

Remarking out the second virtual host made it only bind to the IP of the
first virtual host.  Removing the 'bindaddress' directives and placing
the IP in the <virtualhost> block worked; however, bindaddress
probably should work within the virtualhost block.  :)
>How-To-Repeat:
Use 'bindaddress' in a <virtualhost> block.
>Fix:
Make bindaddress do what you'd expect.  It shouldn't be
that difficult; clearly it already has the ability to bind a virtual
host to an IP address (at least functionally); this would be a
change to the parser.  Alternatively, make a comment in
the documentation / conf file to the effect that bindaddress
only works for the primary server. :%2
>Audit-Trail:
>Unformatted: