The CGI module deliberately makes a unified interface so that you can do:
if (defined ($q->param('foo')) { print "foo is defined!\n"; print "foo = ", $q->param('foo'), "\n"; }

regardless of the means by which the parameters were generated.

Well formed HTML forms either specify a method of POST _or_ GET, not both. Doing both is supported by CGI, but only because the CGI developers are kind to web developers, not because it's an actual part of the CGI standard. More explicitly, you shouldn't generally care which method is used.

If you can provide more information about your problem and what you're trying to accomplish, other monks might be able to help you solve the real issue, as opposed to processing GET and POST simultaneously


In reply to Re: making a difference between POST parameters and URL parameters by Sinistral
in thread making a difference between POST parameters and URL parameters by spx2

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.