You should have no problem with CGI for POST unless you're being given garbage (e.g. being told you are provided something's that "application/x-www-form-urlencoded" when it isn't). 

my $url;
if ($cgi->request_method eq 'GET') {
   # Can't use ->param('url') because the client is
   # providing the parameters in a stupid format.
   ( $url = $ENV{QUERY_STRING} ) =~ s/^.*[?&]url=//s;
} else {
   $url = $cgi->param('url');
}

[download]

If you are getting garbage, it can be handled. You've been given the link to the CGI spec. Read it. Your asking questions with no apparent effort at answering them yourself.

In reply to Re^11: How to parse URL in CGI.pm by ikegami
in thread How to parse URL in CGI.pm by asafp

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.