in reply to Re: Mason via Poet+Plack (FCGI): Request path gets lost
in thread Mason via Poet+Plack (FCGI): Request path gets lost

The docs you are linking to actually include information on how to configure path info and script name, however related to nginx. I'm using Apache 2.4 with mod_fcgid, so the docs loose me here. Tried FcgiFixPathinfo 1 to no avail either. Googling mod_fcgid and script_name reveals PHP-related stuff only beside of e.g. Bug 52710 - mod_fcgid should set PATH_INFO when configured in 'virtual' mode. This bug still has status flag "NEW". Can't quite imagine mod_fcgid is broken like that.

Replies are listed 'Best First'.
Re^3: Mason via Poet+Plack (FCGI): Request path gets lost
by Anonymous Monk on Jun 26, 2014 at 01:03 UTC
    I got a question, you know how you have this 
     
<Location />
    ...
    FcgidWrapper "/usr/local/my_site/bin/start-fcgi.sh" virtual

    [download]

    What tells apache that /anything/whatsoever/here gets served by start-fcgi.sh?

[reply]
[d/l]

      Hi Monk,

      Changing it to <LocationMatch "^/"> has no effect. But I found a work-around (that is, not quite a solution I would call one) which is tweaking the subroutine returned by the builder call in bin/app.psgi that way:

      builder {

    # [...]

    sub {
        my $psgi_env = shift;
        /^\/$/ and $_ = "" for $psgi_env->{SCRIPT_NAME};
        $psgi_env->{PATH_INFO} ||=
            trim( @{$psgi_env}{'SCRIPT_FILENAME', 'DOCUMENT_ROOT'}, ".
+html" );
        $poet->app_class('Mason')->handle_psgi($psgi_env);
    };
};

sub trim {
    my ($string, $head, $tail) = @_;
    $string =~ s{ \A \Q$head\E (.+?) \Q$tail\E \z }{$1}xmsr;
}

      [download]

      What concerns the SCRIPT_NAME line added as well, however, it still does not work.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom