Received: by taz.hyperreal.com (8.8.4/V2.0) id JAA06019; Thu, 13 Feb 1997 09:25:33 -0800 (PST) Received: from Master by taz.hyperreal.com (8.8.4/V2.0) with SMTP id JAA06009; Thu, 13 Feb 1997 09:25:30 -0800 (PST) Date: Thu, 13 Feb 1997 12:08:31 -0500 Message-Id: <97021312083096@decus.org> From: coar@decus.org (Rodent of Unusual Size) To: New-HTTPd@hyperreal.com, Coar@topaz.decus.org Subject: Re: [BUG]: "server-status and server-info can be rewritten in .htaccess" on Irix (fwd) X-VMS-To: NH X-VMS-Cc: COAR Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com >From the fingers of Rob Hartill flowed the following: > >This has comeup before, but I don't remember if the problem was >resolved. the solution is to prevent status/info being triggered from >.htaccess I've been snooping through this, but I don't see a way to do it conveniently. As far as I can tell, there's currently no way an handler can figure out the circumstances of its declaration - mod_mime just stacks it and the handler gets called when the time is right. It knows what the request is, but not at what point it [the hander] was enabled. It looks as though something kludgey could be done if the module had directives to enable/disable the handler (only run the handler if the directive enabled it for the current directory - and don't allow the directive in .htaccess files). If the handler were given the opportunity at declaration time to accept/decline being involved in a particular situation, this could be worked around - but that would be a pretty major change. On the surface, though, it looks to me like it would be a Nice Thing for 2.0. Of course, there's a good likelihood that I'm entirely out to lunch; I'm still feeling my way around this stuff. So how badly have I misunderstood things here? (Be gentle..) #ken :-)}