Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of covener@gmail.com designates
 74.125.82.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=orHC7cEMJSX5tj1Bn00zVqhCYQ8oq5u71PdzsgU/YMnLfu9XW03a5dIAP47+ic5Heb
         8yOWRUNfwuUQe6JQfkWKuyWn8mPP471ox3+/vI0BS3ntNsDsfwNPn/yJbEpPLLqXmzJQ
         c8rGWrmUBPbTNARXiuErFT4s+gnzm2LQ5109I=
MIME-Version: 1.0
In-Reply-To: <AANLkTinjU6Sx9KGfgEBWMXDN+_pkmKbP4m6bsLhZc4-M@mail.gmail.com>
References: <AANLkTikJBU+kJkU1hCBZAS+9V=t_5e+R6bFjupiumFKt@mail.gmail.com>
	<AANLkTinpeH1hUPB9CvVymeVFBzXqxfzufeHVGTkKS2+h@mail.gmail.com>
	<AANLkTikYBHHBgedoDrec2_Nh8wF6F6wV6+kn4P-XYbYT@mail.gmail.com>
	<AANLkTin54VbAf22rk-aO8Sn=nPLC1Qbqg_JKfe4+Q7qD@mail.gmail.com>
	<AANLkTin+h_PSLKt8fe4h+5aK=h75a=4ue2r2Pez_=suU@mail.gmail.com>
	<AANLkTi=KPb_PwvTpKAnmW2-eFfXw4xcg8uSPFu9nQQsS@mail.gmail.com>
	<AANLkTinjU6Sx9KGfgEBWMXDN+_pkmKbP4m6bsLhZc4-M@mail.gmail.com>
Date: Mon, 3 Jan 2011 18:15:59 -0500
Message-ID: <AANLkTimW_VnRqrFy9s5=d0qynm_oRPoUn+NMf1ocv0WU@mail.gmail.com>
Subject: Re: Overriding mod_rewrite from another module
From: Eric Covener <covener@gmail.com>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1

>> The access checking on mod_pagespeed resources is
>> redundant, because the resource will either be served from cache (in which
>> case it had to be authenticated to get into the cache in the first place) or
>> will be decoded and the original resource(s) fetched from the same server
>> with full authentication.

Re: suppressing mod_authz_host: This doesn't sound like it guards
against a user that meets the AAA conditions causing the resource to
be cached and served to users who would not have met the AAA
restrictions.  Maybe you are missing a map_to_storage callback to tell
the core that this thing will really, really not be served from the
filesystem.

Re: suppressing rewrite.  Your comments in the src imply that rewrite
is doing some of what you're also suppressing in
server/core.c:ap_core_translate_name().  Also, it's odd that your
scheme for suppressing mod_rewrite wasn't a no-op for rewrite in
htaccess context, since these use the RUN_ALL fixups hook to do its
magic, but maybe you're catching a break there?