OK I tried to find a more robust alternative but could not. I was thinking
I could duplicate whatever mod_rewrite was doing to set the request filename
that appears to be complex and probably no less brittle.
I have another query on this. In reality we do *not* want our rewritten
resources to
I have implemented Ben's hack in mod_pagespeed in
http://code.google.com/p/modpagespeed/source/detail?r=345 . It works great.
But I am concerned that a subtle change to mod_rewrite.c will break this
hack silently. We would catch it in our regression tests, but the large
number of Apache users
On Mon, Jan 3, 2011 at 4:50 PM, Ben Noordhuis i...@bnoordhuis.nl wrote:
This means that returning OK from my handler does not prevent
mod_authz_host's handler from being called.
You're mistaken, Joshua. The access_checker hook by default is empty.
mod_authz_host is a module and it can be
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
On Mon, Jan 3, 2011 at 6:15 PM, Eric Covener cove...@gmail.com wrote:
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
On Mon, Jan 3, 2011 at 23:19, Joshua Marantz jmara...@google.com wrote:
My goal is not to remove authentication from the server; only from messing
with my module's rewritten resource. The above statement is just observing
that, while it's possible to shunt off mod_rewrite by returning OK from
