comment on

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";
}
[download]

In reply to Re: lighter alternative to CGI.pm by Vennis
in thread lighter alternative to CGI.pm by perrin

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks