If you're reading the data from STDIN, then this implies that you have a broken CGI parser. Generally from the perspective of your program, you should not care whether or not the data is coming via a POST or a GET.

You might want to check out my CGI course, particularly Lesson 2, which explains why hand-rolled parsers are usually broken.

The easiest way to deal with your problem is to use CGI.pm. For example, if the message is in a textarea named "message", you can read it with the following:

    use CGI qw(:standard);
    my $message = param('message');
[download]

Pretty simple, eh? :)

Cheers,
Ovid

New address of my CGI Course.
Silence is Evil (feel free to copy and distribute widely - note copyright text)

I've used the cgi module to recieve simple data sent in a get or a post. The cgi script that I am writing is just for testing to see if the data is correct.

The spec that I am writing for says the data I send shouldn't be sent as a set of key value pairs, but actually in the body of the message. Maybe I'm misinterpreting what they want sent.

Is there a CGI function that will handle this? Anytime I've ever sent anything to a script(through LWP, etc.) I always have sent key value pairs.

Now, you say you have the sending part working; if so, fine. However, you might want to consider using the WWW::Mechanize module to handle the nitty-gritty of talking to cgi forms.

jdporter
The 6th Rule of Perl Club is -- There is no Rule #6.

Do you control the CGI that you're sending data to? Are you using CGI? If not, you should be. It handles all this stuff for you.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

Note: All code is untested, unless otherwise stated

use CGI;
my $cgi = new CGI;
my $message = $cgi->param('keywords');
[download]