Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 53692 invoked from network); 5 Jan 2011 13:58:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Jan 2011 13:58:24 -0000 Received: (qmail 32058 invoked by uid 500); 5 Jan 2011 13:58:24 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 31830 invoked by uid 500); 5 Jan 2011 13:58:22 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 31821 invoked by uid 99); 5 Jan 2011 13:58:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 13:58:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of info@bnoordhuis.nl designates 209.85.213.45 as permitted sender) Received: from [209.85.213.45] (HELO mail-yw0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 13:58:12 +0000 Received: by ywl5 with SMTP id 5so7355285ywl.18 for ; Wed, 05 Jan 2011 05:57:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.102.179 with SMTP id d39mr28477118yhg.62.1294235871338; Wed, 05 Jan 2011 05:57:51 -0800 (PST) Received: by 10.236.110.3 with HTTP; Wed, 5 Jan 2011 05:57:51 -0800 (PST) X-Originating-IP: [195.130.156.9] In-Reply-To: References: Date: Wed, 5 Jan 2011 14:57:51 +0100 Message-ID: Subject: Re: Help trying to figure out why an output_filter is not called. From: Ben Noordhuis To: modules-dev@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 5, 2011 at 14:45, Joshua Marantz wrote: > other filter be somehow finding our filter and killing it? =A0Or sending = the > bytes directly to the network before our filter has a chance to run? Possibly, yes. By the way, why the complex setup? If you don't want the mod_headers filter to run, insert your filter before it, then remove it for each request that you handle.