Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 65519 invoked by uid 500); 19 Sep 2001 21:22:07 -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 65501 invoked from network); 19 Sep 2001 21:22:07 -0000 Date: Wed, 19 Sep 2001 14:21:44 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: ap_custom_response() bug in 1.3? Message-ID: <20010919142144.B12417@ebuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ap_custom_response allocates memory from a request pool and places a pointer to that in a static structure (non-request-pool based). http://bugs.apache.org/index.cgi/full/8334 Slightly older version of same bug: http://bugs.apache.org/index.cgi/full/6336 Anybody care to take a look at the patch included with 8334 and see if it is right? It shifts the custom_response from a global (only needed to be called once) to something that must be called per-request. I think this is the right thing to do though, but I'm not 100% sure. -- justin