httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Hartill <>
Subject [BUG]: "DocumentRoot behaves strangely within VirtualHost" on Irix (fwd)
Date Tue, 28 Jan 1997 11:30:59 GMT

---------- Forwarded message ----------
Date: Mon Jan 27 14:07:19 1997
Subject: [BUG]: "DocumentRoot behaves strangely within VirtualHost" on Irix

Operating system: Irix, version: 6.2
Version of Apache Used: 1.2b6
Extra Modules used: 
URL exhibiting problem: 

When specifying DocumentRoot within a VirtualHost
declaration, the URL *MUST* match the ServerName
specified.  This is a problem specific to using
VirtualHosts.  I'm running another apache server
without VirtualHosts, and I can specify URL's like:
And they all resolv to the full host name, and
the index.html loads each time.  This is not the
case when using virtual hosts...

For example, if I Have:

   DocumentRoot /export/servers/web/root/htdocs

And try to access http://winter/ I get the following
error in my log:  

    access to /usr/local/etc/httpd failed for, reason: File does not exist

But when I access it
works fine.  *BUT* if I change the ServerName to
simple "winter" (without the the
problem is exactly reversed.


This is some more info on my previous bug report:

Adding a "global" DocumentRoot (ouside of the 
VirtualHost) sortof fixes the problem.  It acts
as a "fall-back" DocumentRoot.

For example:  
   When I access: http://winter/ 
              or: http://winter.cs/

   I get the global DocumentRoot.  But when
    I access:
    I get the DocumentRoot specified within
    the VirtualHost declaration.

Also, ServerName doesn't affect the behavior of
DocumentRoot outside the VirtualHost declaration,
as it *DOES* withing a VirtualHOst declatation.

View raw message