Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 1811 invoked by uid 500); 22 Jun 2003 23:48:26 -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 1797 invoked from network); 22 Jun 2003 23:48:25 -0000 Message-ID: <3EF64069.60701@attglobal.net> Date: Sun, 22 Jun 2003 19:48:57 -0400 From: Jeff Trawick Reply-To: trawick@attglobal.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: response handlers get all requests References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Marc M. Adkins wrote: > ... The ap_hook_handler() call > does not specify the handler key from the corresponding AddHandler > configuration directive. As a consequence, the specified handler function > must look at and accept or decline each request.... yep, see most handlers in the modules provided with Apache (mod_autoindex, mod_cgi, etc.) > Is there a rationale for this? dunno > Am I missing a register_hook function that > would allow me to set a key for a response handler? no > I'm looking at trace > statements and my handler must reject PNG files and so forth... your handler needs to look at r->handler and decline stuff that you're not supposed to handle