Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Fri, 18 May 2001 17:43:38 -0700
From: Greg Stein <gstein@lyra.org>
To: new-httpd@apache.org
Subject: Re: Allowing modules to add input filters is broken
Message-ID: <20010518174337.K6482@lyra.org>
Mail-Followup-To: new-httpd@apache.org
References: <Pine.LNX.4.30.0105180955001.12336-100000@koj.rkbloom.net>
 <3B05AB95.68A209DB@sharp.fm>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <3B05AB95.68A209DB@sharp.fm>;
 from minfrin@sharp.fm on Sat, May 19, 2001 at 01:09:09AM +0200

On Sat, May 19, 2001 at 01:09:09AM +0200, Graham Leggett wrote:
>...
> If the result of the request returns a body, then HeaderOut works great.
> If however the result is 304 Not Modified, there is no body, and the
> output filter never runs and we're back to the same problem we had with
> the input filters.
> 
> So the question is - which hook should be called to fiddle with the
> headers after the content generator runs, but before the headers are
> sent to the network, whether a body exists or not...?

The output filters should *always* run, if at least to send an EOS bucket.
That EOS is actually what triggers the delivery of the headers to the
network (or at least to the CORE filter for output buffering into the next
request).

So if you're not seeing output filters run, then a bug exists.

(IOW: theory says you're doing the right thing)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/