"Your request path doesn't match your Location" #352

Open
johto opened this Issue Nov 21, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@johto

johto commented Nov 21, 2012

Hi,

Given this Apache2 configuration:

<Location /foo>
SetHandler perl-script
PerlResponseHandler Plack::Handler::Apache2
PerlSetVar psgi_app bar.psgi

Doing a request to http://server.name//foo gives me this error:

Your request path is '//foo' and it doesn't match your Location(Match) '/foo'. This should be due to the configuration error. See perldoc Plack::Handler::Apache2 for details.

"perldoc Plack::Handler::Apache2" didn't tell me anything useful, and this doesn't look like a configuration error to me.

Thoughts?

@miyagawa

This comment has been minimized.

Show comment Hide comment
@miyagawa

miyagawa Nov 21, 2012

Member

Do you actually have a Location block to contain that SetHandler? If so what is it?

Member

miyagawa commented Nov 21, 2012

Do you actually have a Location block to contain that SetHandler? If so what is it?

@johto

This comment has been minimized.

Show comment Hide comment
@johto

johto Nov 21, 2012

Oops. I had it in my original post, but it got eaten by the github formatting. I'll try again:

<Location /foo>
        SetHandler perl-script
        PerlResponseHandler Plack::Handler::Apache2
        PerlSetVar psgi_app bar.psgi
</Location>

johto commented Nov 21, 2012

Oops. I had it in my original post, but it got eaten by the github formatting. I'll try again:

<Location /foo>
        SetHandler perl-script
        PerlResponseHandler Plack::Handler::Apache2
        PerlSetVar psgi_app bar.psgi
</Location>
@miyagawa

This comment has been minimized.

Show comment Hide comment
@miyagawa

miyagawa Nov 21, 2012

Member

OK, yeah this is how Apache is munging double slashes into one internally while keeping that in the request URI, messing up the handler's match.

This is arguably an Apache bug or at least weird behavior, and maybe we have to work around by munging slashes into one or something.

Member

miyagawa commented Nov 21, 2012

OK, yeah this is how Apache is munging double slashes into one internally while keeping that in the request URI, messing up the handler's match.

This is arguably an Apache bug or at least weird behavior, and maybe we have to work around by munging slashes into one or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment