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.

In reply to Re^4: Mason via Poet+Plack (FCGI): Request path gets lost by flowdy
in thread Mason via Poet+Plack (FCGI): Request path gets lost by flowdy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.