While you're editing script maps, you could also fix a few of the security issues in IIS. For example Code Red worm and $DATA vulnerabilites. Add the following code after the $script_maps{'.plx'} line... 
#
#   Protects against $DATA stream hack which gives
#   everyone access to your source code
#
$script_maps{'.pl:$DATA'} = $script_maps{'.pl'};
$script_maps{'.cgi:$DATA'} = $script_maps{'.cgi'};
$script_maps{'.plx:$DATA'} = $script_maps{'.plx'};

#
#   Protects against Code Red Worm by removing
#   the Index Server script mappings
#
delete $script_maps{'.ida'};
delete $script_maps{'.idq'};

[download]
Error: Keyboard not attached. Press F1 to continue.

In reply to Re: Fix ActiveState Script Maps (IIS) by $code or die
in thread Fix ActiveState Script Maps (IIS) by $code or die

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.