Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of torsten.foertsch@gmx.net
 designates 213.165.64.22 as permitted sender)
Message-ID: <50A3AB44.9050107@gmx.net>
Date: Wed, 14 Nov 2012 15:31:32 +0100
From: =?UTF-8?B?VG9yc3RlbiBGw7ZydHNjaA==?= <torsten.foertsch@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: mod_perl list <modperl@perl.apache.org>
CC: =?UTF-8?B?QW5kcsOpIFdhcm5pZXI=?= <aw@ice-sa.com>
Subject: Re: question on sub-requests
References: <50A12FBB.2070607@ice-sa.com> <50A23900.4060202@gmx.net>
 <50A28ECD.7010103@ice-sa.com> <50A3886A.7010601@gmx.net>
 <50A3A129.209@ice-sa.com>
In-Reply-To: <50A3A129.209@ice-sa.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 11/14/2012 02:48 PM, André Warnier wrote:
> I my particular case, the sendfile() solution above works fine, because
> I am sure in this case that no additional processing needs to take place
> on those static pages.

What I meant in particular was the HTTP code 304 generation. With your
solution the browser will always get a fresh copy even if the cache is
still valid.

> About returning DECLINED in a ResponseHandler : that works fine, and
> apparently has the effect of Apache serving the resource using it's
> default handler (or, I suppose, any other alternative response handler
> that may be chained).  This is consistent with the fact that a response
> handler is of type
> 
> quote
> RUN_FIRST

That's why I thought returning DECLINED should work. If you want to
switch to dedicated handler other than the default one I think you can
set it via $r->handler(newhandler). But in this case you have to hope
that the new handler is further down the handler chain. Modperl
registers its 2 response handlers with APR_HOOK_MIDDLE. So, it may
depend on the LoadModule order whether the modperl handler comes first
or newhandler.

Torsten