CGIs derive their parameters from either $ENV{'QUERY_STRING'} or <STDIN> (or both!), while Getopt::Long expects everything to be in @ARGV.

Converting one to the other is trivial ...

my $extract; my $file; { local @ARGV = split /&/, $ENV{'QUERY_STRING'}; GetOptions( 'file=s' => \$file, 'extract!' => \$extract, ); }

That'll break if you have URI-escaped characters (ie, %7E instead of ~), so a more robust solution would be to iteratively build @ARGV using CGI's param funcs.

my $extract; my $file; { local @ARGV; foreach my $key ( param ) { if ( param($key) ) { foreach my $value ( param($key) ) { push @ARGV, $key, $value; } } else { # arg-less booleans push @ARGV, $key; } } GetOptions( 'file=s' => \$file, 'extract!' => \$extract, ); }

In reply to Re: Why does Getopt::Long ignore browser and SSI-based parameters? by Kanji
in thread Why does Getopt::Long ignore browser and SSI-based parameters? by ayurkowski

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.