CGI::NoPoisonCGI::NoPoison is No Poison Null Byte in CGI->Vars. | |
Download |
CGI::NoPoison Ranking & Summary
Advertisement
- License:
- Perl Artistic License
- Price:
- FREE
- Publisher Name:
- Scott R. Godin
- Publisher web site:
- http://search.cpan.org/~sgodin/Time-Elapse-1.2402/Elapse.pm
CGI::NoPoison Tags
CGI::NoPoison Description
CGI::NoPoison is No Poison Null Byte in CGI->Vars. CGI::NoPoison is No Poison Null Byte in CGI->Vars.SYNOPSIS use CGI; use CGI::NoPoison my $m = CGI->new(); $m->param( -name=>'amplifier', -value=>, ); my %h = $m->Vars(); # look ma, no splitting on poison null-bytes ( '' )! print "$_ => ", join ", ", @{$h{$_}} for keys %h; print "This one goes ", ($m->param('amplifier'));Simplicity itself. Instead of using a null-byte to separate multi-valued fields why not just use what CGI.pm already uses to store the values internally?"What's that?", you ask? Why, it's an anonymous array, of course, like anyone sensible would use. cgi-lib.pl may have been fine years and years ago, but this now-archaic throwback no longer needs us to bow to its demands. (is anyone still actually using it? yikes.)This does, however change how you parse CGI->Vars() (as an anon-array, not a -packed string) and also how you set params.NOW you can properly test for inserted null-bytes in a secure environment WHILE taking advantage of the convenience of the Vars() function. Requirements: · Perl
CGI::NoPoison Related Software