Mailing List Archive

Suggestion for Apache Server (fwd)
For any virtual host gurus to ponder...

no ack sent.

Forwarded message:
> From kevin@myhost Sun Oct 15 13:58:13 1995
> Message-Id: <9510152206.AA00282@myhost.digex.net>
> Content-Type: text/plain
> Mime-Version: 1.0 (NeXT Mail 3.3 v118.2)
> From: Kevin Kim <kevin@myhost>
> Date: Sun, 15 Oct 95 17:06:49 -0500
> To: apache-bugs@mail.apache.org
> Subject: Suggestion for Apache Server
> Reply-To: kykim@access.digex.net
>
> Hi,
>
> We set our users up with an account with directories "WWW" and "cgi-bin" to
> put there web page stuff in. We configure the Apache server to use the
> directories "/usr/home/username/WWW" as the DocumentRoot for each Virtual
> Host.
>
> But, we have some users who rename "WWW" to "www". As a result, the Apache
> server won't start. Is there anyway to have so that the Apache server just
> ignores the VIrtual Host that has incorrect configuration information, but
> starts the rest? It could just log an error message in the top-level error
> log about not starting the Virtual Host.
>
> Thanks,
> -kevin
> Kevin Kim
>
Re: Suggestion for Apache Server (fwd) [ In reply to ]
Last time, Rob Hartill uttered the following other thing:
>
>
> For any virtual host gurus to ponder...
>
> no ack sent.
>
> Forwarded message:
> >
> > Hi,
> >
> > We set our users up with an account with directories "WWW" and "cgi-bin" to
> > put there web page stuff in. We configure the Apache server to use the
> > directories "/usr/home/username/WWW" as the DocumentRoot for each Virtual
> > Host.
> >
> > But, we have some users who rename "WWW" to "www". As a result, the Apache
> > server won't start. Is there anyway to have so that the Apache server just
> > ignores the VIrtual Host that has incorrect configuration information, but
> > starts the rest? It could just log an error message in the top-level error
> > log about not starting the Virtual Host.

This was also brought up by members of the NCSA HTTPd beta test,
and a "fix" is implemented in 1.5b6

If you want configuration compatibility:
basically, we added a keyword to the VirtualHost line

<VirtualHost 127.0.0.1 Required>
...
</VirtualHost>

If anything in this configuration fails, the server exits.

Or

<VirtualHost 127.0.0.1 Optional>
...
</VirtualHost>

Any errors just log warnings. All other servers should work fine,
behaviour of the error'd host is undefined (I could probably make
it just not exist, but that's not currently what it does, it just
tries to work as well as it can)

If you don't add the keyword, it defaults to Required (backward
compatible).

Kinda a hack, but . . .

Brandon

--
Brandon Long (N9WUC) "I think, therefore, I am confused." -- RAW
Computer Engineering Run Linux '95. It's that Easy.
University of Illinois blong@uiuc.edu http://www.uiuc.edu/ph/www/blong
Don't worry, these aren't even my views.
Re: Suggestion for Apache Server (fwd) [ In reply to ]
On Sun, 15 Oct 1995, Brandon Long wrote:
> If you want configuration compatibility:
> basically, we added a keyword to the VirtualHost line
>
> <VirtualHost 127.0.0.1 Required>
> ...
> </VirtualHost>
>
> If anything in this configuration fails, the server exits.
>
> Or
>
> <VirtualHost 127.0.0.1 Optional>
> ...
> </VirtualHost>
>
> Any errors just log warnings. All other servers should work fine,
> behaviour of the error'd host is undefined (I could probably make
> it just not exist, but that's not currently what it does, it just
> tries to work as well as it can)
>
> If you don't add the keyword, it defaults to Required (backward
> compatible).
>
> Kinda a hack, but . . .

No, I like it - we did mods here that simply printed out to stderr (since
the log files hadn't been opened yet) that there was no directory for the
document root, but proceeded to run. Can't locate those right now,
though....

Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/