Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 78965 invoked by uid 500); 30 Jun 2003 16:29:18 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 78951 invoked from network); 30 Jun 2003 16:29:18 -0000 Date: Mon, 30 Jun 2003 09:29:24 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: Re: AddHandler scope Message-ID: <2147483647.1056965364@[10.0.1.29]> In-Reply-To: References: X-Mailer: Mulberry/3.1.0b2 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=0.0 required=5.0 tests=none version=2.60-cvs X-Spam-Checker-Version: SpamAssassin 2.60-cvs (1.186-2003-05-09-exp) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --On Sunday, June 29, 2003 2:05 PM -0700 "Marc M. Adkins" wrote: > I've been working on a module and quite unexpectedly I found that my > AddHandler directive was taking affect at a global level even though it was > defined within a virtual host block. So it was affecting Apache manual > pages that weren't in the virtual host for which I had created the > AddHandler directive. Am I misunderstanding the scope of AddHandler? > > I am using named virtual host. For testing I have all of the named hosts > defined in my HOSTS file to point to 127.0.0.1. So in a sense it all goes > to the same place. I wouldn't have thought that would have made a > difference. Hmm, considering AddHandler is implemented by mod_mime, I would find it very suspicious that this is behaving this way. Can you please post a configuration snippet that demonstrates this behavior? -- justin