Well, by requesting without the trailing "/" you're asking for a file named "script_dir", which apache is then doing an internal redirect to the directory "/script_dir/." Apache is then picking up your rule that sets the default to index.cgi after the internal redirect.

It isn't that suprising, at least to me, that you'd lose the environment variables, including the posted data because of the redirect.

When you request "script_dir/" with the trailing slash, you're avoiding the needed internal apache redirect, and keeping the environment variables.

That's a long way to say "always end requests for directories with a trailing slash for performance's sake, and CGI.pm is still the bomb."

In reply to Re: CGI.pm bug? Or Apache issue? by Teenage Mutant Ninja Camel
in thread CGI.pm bug? Or Apache issue? by cLive ;-)

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.