After reading in LStein's book, your use of $r->subprocess_env seems to be the wrong approach. "Changes made to the environment table only persist for the length of the request. The table is cleared out and reinitialized at the beginning of every transaction." (pg.455)

On pg. 437, it is noted that changing the path_info() requires syncing the uri() to the update. As in: 

my $path_info = $r->path_info;
my $uri = $r->uri;
my $orig_uri = substr $uri, 0 length($uri) - length($path_info);
$r->path_info($path_info . $step);
$r->uri($orig_uri . $r->path_info);

[download]

In reply to Re: mod_perl and propogating path_info by Lhamo Latso
in thread mod_perl and propogating path_info by derby

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.