In fact, I think that's nothing to do with RFC. A CGI script can be in Perl, Python, PHP, or whatever, it's the spec only, which is a "WHAT" but I am asking "HOW".
Consider I have already prepare everything (is needed for me at this moment, actually), but as said in my OP, the limitation is I have to do all the rest within my server's code. My server can communicate with the browser by all means.
I don't know "the how" is how to pass the parameters that I've prepared to my target CGI script, so when my CGI script got triggered, it's just naturally have all the %ENV variables ready or a opened STDIN is ready for read().
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.