hash to query string using semicolon

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

Replies are listed 'Best First'.
Re: hash to query string using semicolon by Corion (Patriarch) on Feb 16, 2009 at 22:05 UTC
What's wrong with using just CGI? `use strict; use CGI; my $c=CGI->new(); $c->param('foo'=>'bar'); $c->param('baz'=>'boo'); print $c->url(-query=>1,-relative=>1); __END__ ?foo=bar;baz=boo` [download]	[reply] [d/l]
Re: hash to query string using semicolon by jasonk (Parson) on Feb 16, 2009 at 22:18 UTC
URI::QueryParam doesn't use anything for query parameters, it just passes it's data on to URI, which lets you choose how they are delimited... `use URI; my $u = URI->new( "http://www.example.com/" ); $u->query_form( { foo => 1, bar => 2 }, ';' ); print "$u\n";` [download] And if you just want the query string, you can get it from `$u->query`. www.jasonkohles.com We're not surrounded, we're in a target-rich environment!	[reply] [d/l] [select]
Re: hash to query string using semicolon by ikegami (Patriarch) on Feb 16, 2009 at 22:10 UTC
`use URI::Escape qw( uri_escape ); my $query = '?' . join ';', map { uri_escape($_->[0]) .'='. uri_escape($_->[1]) } @query_args;` [download] Update: Oops, Forgot there are keys and values rather than just values. Fixed.	[reply] [d/l]
Re: hash to query string using semicolon by Your Mother (Archbishop) on Feb 17, 2009 at 00:20 UTC
And you don't have to go all the way to QueryParam; depending on your needs. URI proper supports it now: `$uri->query_form( \%hash, $delim )`.	[reply] [d/l]
Re^2: hash to query string using semicolon by Your Mother (Archbishop) on Apr 12, 2019 at 00:34 UTC
I should have included that this can be set globally with `$URI::DEFAULT_QUERY_FORM_DELIMITER = ";";`. I know it's mildly controversial with the current RFCs but the `&` as standard was always a mistake since it effectively made real world separators the incredibly clunky `&`. As long as you support or know the receiving end supports the semicolon, I think it's the best practice. While I'm telling you kids to get off my lawn, the `?arg[0]=foo&arg[1]=bar` crap we got from PHP and ruby webdevs being unable to parse naked lists in order is also a travesty.	[reply] [d/l] [select]