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: domain of jmarantz@google.com
 designates 74.125.121.67 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=google.com; s=beta;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=wWI/nrXIJHs+1x1AsogymA+xVrPEaOKfhZDVU+Ga39YWNlUa0fPltAZogkp2zVZt0l
         eoH4VCgVtSUl4WXEyAMw==
MIME-Version: 1.0
In-Reply-To: <AANLkTinpeH1hUPB9CvVymeVFBzXqxfzufeHVGTkKS2+h@mail.gmail.com>
References: <AANLkTikJBU+kJkU1hCBZAS+9V=t_5e+R6bFjupiumFKt@mail.gmail.com>
 <AANLkTinpeH1hUPB9CvVymeVFBzXqxfzufeHVGTkKS2+h@mail.gmail.com>
From: Joshua Marantz <jmarantz@google.com>
Date: Fri, 31 Dec 2010 18:16:08 -0500
Message-ID: <AANLkTikYBHHBgedoDrec2_Nh8wF6F6wV6+kn4P-XYbYT@mail.gmail.com>
Subject: Re: Overriding mod_rewrite from another module
To: modules-dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=002215048fb7f6248c0498bcfd66

--002215048fb7f6248c0498bcfd66
Content-Type: text/plain; charset=ISO-8859-1

Thanks for the quick response and the promising idea for a hack.  Looking at
mod_rewrite.c this does indeed look a lot more surgical, if, perhaps,
fragile, as mod_rewrite.c doesn't expose that string-constant in any formal
interface (even as a #define in a .h).  Nevertheless the solution is
easy-to-implement and easy-to-test, so...thanks!

I'm also still wondering if there's a good source of official documentation
for the detailed semantics of interfaces like ap_hook_translate_name.
 Neither a Google Search, a  stackoverflow.com search, nor the Apache
Modules<http://www.amazon.com/Apache-Modules-Book-Application-Development/dp/0132409674/ref=sr_1_1?ie=UTF8&qid=1293837117&sr=8-1>book
offer much detail.
code.google.com fares a little better but just points to 4 existing usages.

-Josh

On Fri, Dec 31, 2010 at 1:50 PM, Ben Noordhuis <info@bnoordhuis.nl> wrote:

> On Fri, Dec 31, 2010 at 18:17, Joshua Marantz <jmarantz@google.com> wrote:
> > Is there a better way to solve the original problem: preventing
> mod_rewrite
> > from corrupting mod_pagespeed's resources?
>
> From memory and from a quick peek at mod_rewrite.c: in your
> translate_name hook, set a "mod_rewrite_rewritten" note in r->notes
> with value "0" and return DECLINED. That'll trick mod_rewrite into
> thinking that it has already processed the request.
>

--002215048fb7f6248c0498bcfd66--