I personnally wouldn't use the next code and strongly advice to create a better running server...
But, FYI, you can parse the parameters manually. Depending on the complexity, you could use this.
If you use this 'wannahave a Big Ball of Mud solution' (i love that name) make sure you check the parameters for security problems.
my $input;
if ($ENV{REQUEST_METHOD} eq 'GET'){
$input = $ENV{QUERY_STRING};
} else {
read(STDIN,$input,$ENV{CONTENT_LENGTH});
}
foreach( split(/&/,$input)){
$_ =~ tr/+/ /;
my ($name,$value) = split(/=/,$_,2);
$name =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C",hex($1))/eg;
$value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C",hex($1))/eg;
if($param{$name}) {
$param{$name}.= ",$value";
} else {
$param{$name} = $value;
}
print "Found $name = $value\n";
}
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.