httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <>
Subject Re: [STATUS] 1.3
Date Mon, 07 Jul 1997 00:15:12 GMT
I think the real long-term solution to this is replacing AllowOverride
(well, expanding; we still want to be able to control groups of
directives) with the ability to control individual directives, including
what arguments can be given.  The problem is that this is a major change
so it hasn't been done yet.

On Sun, 6 Jul 1997, Brian Behlendorf wrote:

> Philosophically, I'm not comfortable with the idea of one directive
> specifically for disabling another.  Let's say Alexei proposes HandlerMatch
> - do we keep up and propose DisableHandlerMatch?  
> We already have a method for controlling access to directives, and that's
> using the groups as controlled by an "AllowOverride" directive.  Right now
> to prevent the problem one could say "AllowOverride None" or any
> replacement for "None" except for "FileInfo".  However users then wouldn't
> be able to add new MIME types or error documents, most noticeably.  
> If what we're saying is that the "status" functionality shouldn't be
> grouped with the others in FileInfo, then we have a problem with a
> directive which goes beyond its original purpose.  One option is to have
> the status module triggered not by a file type handler (which has always
> confused me) but instead a directive unique for the status page, i.e.
> "ShowStatus".  That directive can
> be separately scoped.
> Of course that would break backwards compatibility, and we might want to
> save breaking things like that for 2.0.  
> Perhaps another option - can the status module check to see where it was
> triggered from?  And only allow it to be set in the server resource files?
> 	Brian
> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
> "Why not?" - TL       - -

View raw message