Handler::Apache2::fixup_path messes up SCRIPT_NAME

[damil]

Context

I'm using modperl PerlAuthz handlers to control access to some parts of
my application, i.e. the Apache config looks more or less like this:

<Location /my_app>
SetHandler modperl
PerlResponseHandler My::Catalyst::App
PerlOptions +ParseHeaders
PerlOptions +SetupEnv

<LocationMatch "^/my_app/(foo|bar)/restricted">
PerlAuthzHandler My::Authorization::Module
# authz configuration options

<LocationMatch "^/my_app/(other|area)/restricted">
...

Problem

fixup_path() in Handler/Apache2.pm misinterprets the config.
When it calls $r->location, modperl returns the inner LocationMatch
directive, but that directive is just for authorization, it's not the
root of the application. Then $env->{SCRIPT_NAME} is incorrectly set to
the inner URL, whereas $ENV{SCRIPT_NAME} as given through
Apache+mod_perl is correct.

I don't really understand why this fixup_path() business is necessary,
since Apache+mod_perl already seems to do the proper job; but anyway,
if you need to keep that code, I guess there should be an additional
check to execute it only when running under ModPerl::Registry, not when
running under other modperl handlers.

For the moment, I hacked the "prepare_path" method in my Catalyst app
to work around this problem.

[damil]

Sorry, the config example was messed up because of markdown rules. Here it is again :

<Location /my_app>
    SetHandler modperl
    PerlResponseHandler My::Catalyst::App
    PerlOptions +ParseHeaders
    PerlOptions +SetupEnv
</Location>

<LocationMatch "^/my_app/(foo|bar)/restricted">
    PerlAuthzHandler My::Authorization::Module
    # authz configuration options
</LocationMatch>


<LocationMatch "^/my_app/(other|area)/restricted">
    ...
</LocationMatch>