http POST replies

dmsparts has asked for the wisdom of the Perl Monks concerning the following question:

i am trying to setup a script that will accept POST replies and write them into a text file. i can get it to work with the GET action but the website that is sending the info is using POST and cannot cahnge it, at the moment i have,


sub smsreply {

$smsreply = 'd:\inetpub\wwwroot\cgi-bin\classads\test';


{ local ($buffer, @pairs, $pair, $name, $value, %FORM)}; 

# Read in text 

$ENV{'REQUEST_METHOD'} =~ tr/a-z/A-Z/;

if ($ENV{'REQUEST_METHOD'} eq "POST") { read(STDIN, $buffer, $ENV{'CON
+TENT_LENGTH'}); } 

else { $buffer = $ENV{'QUERY_STRING'}; } 

# Split information into name/value pairs 

@pairs = split(/&/, $buffer); 

foreach $pair (@pairs) { ($name, $value) = split(/=/, $pair); $value =
+~ tr/+/ /;

$postFields{ "$name" } = $value;

$from = $postFields{ "from" };
$msg = $postFields{ "text" };
$msgid = $postFields{ "msgid" };

$msg =~ s/%(..)/pack("C", hex($1))/eg;

open (SMSREPLY, ">>$smsreply/$msgid.txt");
print SMSREPLY "\n$from $msg $msgid";
close SMSREPLY;
  }


}
[download]

any help will be appreciated Michael I have now got the script working but i neet to make it retuen a HTTP 200 status back to the server that calls the script once it has executed. I cannot find any way to do this. Please help. Cheers

Comment on http POST replies Download Code

Replies are listed 'Best First'.
Re: http POST replies by olus (Curate) on Aug 19, 2008 at 11:57 UTC
`use CGI; my $query = new CGI; my $msgid = $query->param('msgid'); my $from = $query->param('from'); my $msg = $query->param('msg'); # Now do what you want with the params` [download]	[reply] [d/l]
Re: http POST replies by Anonymous Monk on Aug 19, 2008 at 11:56 UTC
use CGI; or use CGI::Simple; or use CGI::Lite;	[reply]
Re^2: http POST replies by Anonymous Monk on Aug 19, 2008 at 12:00 UTC
http://search.cpan.org/~lds/CGI.pm-3.40/CGI.pm#CREATING_A_FILE_UPLOAD_FIELD http://search.cpan.org/src/LDS/CGI.pm-3.40/examples/file_upload.cgi http://search.cpan.org/~andya/CGI-Simple-1.105/lib/CGI/Simple.pm#FILE_UPLOADS http://search.cpan.org/src/SMYLERS/CGI-Lite-2.02/examples/upload	[reply]
Re: http POST replies by zentara (Archbishop) on Aug 19, 2008 at 12:57 UTC
It would go something like this: `#!/usr/bin/perl use warnings; use CGI 'cgi'; my $cgi = new CGI; my $relay = ''; my %input= $cgi->Vars(); foreach $name (keys %input){ my $value = $input{$name}; $relay .= "$name=$value&"; } open (RT,">respgen.test"); print RT $relay; close RT;` [download] I'm not really a human, but I play one on earth Remember How Lucky You Are	[reply] [d/l]
Re^2: http POST replies by dmsparts (Sexton) on Aug 19, 2008 at 13:11 UTC
thanks, have tried your suggestion and just gst CGI errors	[reply]
Re^3: http POST replies by Anonymous Monk on Aug 19, 2008 at 13:27 UTC
CGI Help Guide	[reply]
Re^3: http POST replies by CountZero (Bishop) on Aug 19, 2008 at 15:46 UTC
Exactly what have you tried and which errors did you get? CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]
Re: http POST replies by SFLEX (Chaplain) on Aug 19, 2008 at 12:29 UTC
Like everyone said above me CGI or a module alike for your form inputs, but as i look at your code your getting the file name from a form input so using taint or make sure that name does not go out of its boundary's. Unless you are 100% sure that only trusted people will be using that code only.	[reply]
Re^2: http POST replies by Anonymous Monk on Aug 19, 2008 at 12:38 UTC
Another way is to generate (perhaps with Data::UUID) a safe filename (ex fooBAR), and create associated metadata file (fooBAR.meta) that contains uploaded name, uploader ...	[reply]
Re: http POST replies by geira (Initiate) on Aug 19, 2008 at 12:48 UTC
Naturally this depends on the client sending RFC-valid `param=value` pairs. Most web services don't, in case you ever venture into that territory.	[reply] [d/l]


Welcome to the Monastery
	PerlMonks