I would tend to agree with Ryan here, it should not be assumed that the request_rec will be available in the core_output_filter. One possible solution would be to have c->bytes_in and c->bytes_out, then have identical fields in the request_rec that would be updated upon the completion of the request. (counting only the bytes sent during *that* request) I gave this a try a while back, but ran into problems because the request processing can bail out and run ap_log_transaction whenever it wants. (on 404's, etc). The request processing in apache is not symmetrical enough for that approach.
Then there's the issue of counting the bytes in the set-aside buckets from buffered output (like Brian mentioned), but thats another problem altogether. -Ryan On Tue, Sep 17, 2002 at 11:22:03PM -0400, [EMAIL PROTECTED] wrote: > > You don't want to do this. A connection based filter is connection > oriented. By definition, it has no concept of a request. While this > might make sense for HTTP, other protocol modules will have a much harder > time with this change. > > Ryan > > On 18 Sep 2002, Bojan Smojver wrote: > > > Justin, > > > > After mucking around a bit with what you suggested, this seemed like the > > straightforward thing to do. Not sure how things would work on internal > > redirects etc. Can you please have a look. I'm sure it's naive, but so > > am I (for now :-) > > > > Bojan > > > > -- > > _______________________________________________________________________________ > Ryan Bloom [EMAIL PROTECTED] > 550 Jean St > Oakland CA 94610 > ------------------------------------------------------------------------------- > >
