Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4A8A4C6D.5050409@nauticaltech.com>
Date: Mon, 17 Aug 2009 23:38:37 -0700
From: Michael Spiegle <mike@nauticaltech.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: modules-dev@httpd.apache.org
Subject: Re: [Fwd: Re: Having some issues with subrequests and filters]
References: <4A874E1B.7070301@apache.org>
In-Reply-To: <4A874E1B.7070301@apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Nick Kew wrote:
> Michael Spiegle wrote:
>> Hello,
>> I have a module I am writing which implements a content-generator and
>> a filter.  If I make a sub-request from within my content-generator,
>> the filter's (request_rec*)f->r only points to the original request.
>> How do I access the current sub-request from within my filter?
>
> How do you know the subrequest exists at the point where you access
> it from the filter?
>
> Put whatever you need on your module's filter's context.
>


I was hoping that when my filter starts receiving data for a subrequest, 
the request_rec* attached to the filter would indicate that it was a 
subrequest via f->r->main not being NULL.  It seems like you can use 
that logic everywhere else, so why not in the filter context?