Without using GET parameters, you only have a couple different possibilities.

Big Kludge (not recommended) - Use LWP to submit the query and get the HTML, then display to the client. The query doesn't come from the browser so hokey stuff is going to happen.

Cookies - Store the information in cookies and then redirect.

Sessions - Give each user a unique session ID every time they login and pass that with GET. Store the information that needs to be submitted in a flat file or database.

The reason for all this is because POST works by sending the input through STDIN. That means you can't cleanly recreate it on the server side because the client must be involved to properly use POST.

In reply to Re: Passing CGI parameters on new CGI by comatose
in thread Passing CGI parameters on new CGI by Michalis

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.