You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by jason andrade <ja...@dstc.edu.au> on 1997/07/31 15:20:01 UTC

config/953: Migrating from 1.1.3 -> 1.2.1 breaks all my _NON_ virtualhost (ie main server) directives.

>Number:         953
>Category:       config
>Synopsis:       Migrating from 1.1.3 -> 1.2.1 breaks all my _NON_ virtualhost (ie main server) directives.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jul 31 06:20:00 1997
>Originator:     jason@dstc.edu.au
>Organization:
apache
>Release:        1.2.1
>Environment:
DEC UNIX 4.0B, apache compiled with DEC cc.

External server, runs with multiple virtual ip#s, specifically 3 ip#s bound to
the one interface.
>Description:
I'm currently using apache 1.1.3, and decided to migrate to 1.2.1 across our
3 main servers. we have this configured so that 2 internal servers, run with
one being Main and the other a Virtualhost, and 3 external servers run
with one being Main and the other 2 defined in Virtualhost.

Under 1.1.3, this works perfectly. e.g

http://www.dstc.edu.au goes to /www/public/htdocs
http://webpages.dstc.edu.au goes to /www/webpages/htdocs
http://metadata.net goes to /www/metadata/htdocs

Under 1.2.1, this breaks completely for me, and all requests go to the first
Virtualhost only, e.g

http://www.dstc.edu.au goes to /www/webpages/htdocs
http://webpages.dstc.edu.au goes to /www/webpages/htdocs
http://metadata.net goes to /www/webpages.htdocs

if i kill the 1.2.1 server and go back to 1.1.3, then it works fine again.

the conf files are unchanged between the two versions, so i'm at a loss to
understand why the server appears to ignore the Main server directive.

i've had a look through the problem database, and can summarise with

"Virtualhosts are broken in 1.2, either dont use them, or dont try and
use the main server, instead putting everything into Virtualhosts".

Before i am forced to do this, is there any possibility this is a
reproducible bug and might be fixed (or if you know of what i might
be doing to cause this..)

An example of one of my virtualhost directives is

#
<VirtualHost webpages.dstc.edu.au>
ServerAdmin     brads@dstc.edu.au
DocumentRoot    /www/webpages/htdocs/
ServerName      webpages.dstc.edu.au
ErrorLog        /var/www/webpages/logs/error_log
TransferLog     /var/www/webpages/logs/access_log
ResourceConfig  /www/public/conf/webpages_srm.conf
</VirtualHost>
#


>How-To-Repeat:
http://www.dstc.edu.au (currently on 1.1.3).
http://webpages.dstc.edu.au (virtual)
http://metadata.net         (virtual)

if you email me, i'll be able to put up the 1.2.1 server and you can observe the
behaviour of the above urls.
>Fix:
work out what changed in virtual host handling between 1.1.3 and 1.2.1 ? :-)

since i'm using a very similar Configuration file, and the conf files are
identical, its hard for me to see why virtual hosts are broken for me
>Audit-Trail:
>Unformatted: