Re: CGI::Vars weirdness

I am confused by you problem.

If you would like to have the QUERY_STRING directly you can parse $ENV{QUERY_STRING};

my @values = split(/&/,$ENV{QUERY_STRING});
foreach my $i (@values) {
    my ($name, $value) = split(/=/, $i);
    push(@{$keys{$name}}, $value);
}
[download]

Note that this has a slightly different structure that the structure ruturned by CGI::Vars.

-- gam3
A picture is worth a thousand words, but takes 200K.

Comment on Re: CGI::Vars weirdness Download Code

Replies are listed 'Best First'.
Re^2: CGI::Vars weirdness by chromatic (Archbishop) on Apr 04, 2008 at 05:38 UTC
The semicolon is also a valid separator for key-value pairs in URL-encoded query strings... but don't parse query strings by hand. You'll get it wrong.	[reply]
Re^3: CGI::Vars weirdness by ikegami (Patriarch) on Apr 04, 2008 at 06:50 UTC
Not quite. "`;`" is a valid separator for HTTP URLs, but not for application/x-www-form-urlencoded (i.e. form) data. In other words, you may assign URLs any meaning you wish to "`;`" in URLs to resources you control, but it's by no means equivalent to "`&`" unless you choose it to be for those resources. You shouldn't impose your choice as fact onto others.	[reply] [d/l] [select]