Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Subject: Re: Counting bytes_sent in core output_filter Re: [PATCH: Apache
	2.0] mod_log_config: input/output bytes
From: Bojan Smojver <bojan@rexursive.com>
To: Apache Dev List <dev@httpd.apache.org>
In-Reply-To: <20020821073718.GQ14713@apache.org>
References: <1029822380.1396.114.camel@beast.rexursive.com>
	<20020820062013.GD14713@apache.org>
	<1029844483.1396.191.camel@beast.rexursive.com>
	<20020820165905.GF14713@apache.org> <3D6340E1.3000609@apache.org>
	<20020821073718.GQ14713@apache.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 21 Aug 2002 21:49:15 +1000
Message-Id: <1029930555.1348.3.camel@beast.rexursive.com>
Mime-Version: 1.0

On Wed, 2002-08-21 at 17:37, Justin Erenkrantz wrote:
> On Wed, Aug 21, 2002 at 12:27:29AM -0700, Brian Pane wrote:
> > The remaining problem is: how can we identify the request_rec from
> > within core_output_filter()?  Within that filter, f->r is NULL.  I
> > have some ideas for solving this by putting some metadata in the
> > brigade to associate each EOS with the corresponding request.
> > But is there a better solution that already exists for getting
> > the request_rec?
> 
> Actually, I thought it was already fixed, but you're right the
> connection filters don't yet have access to f->r.

I think you are right, actually. The CVS version of http_protocol.c is
different then the one from Apache 2.0.40. It contains a function
update_r_in_filters(), which (I think) does that. Or maybe it's just
wishful thinking on my behalf? 

Bojan