use URI;
my $user_url = "http://www.stonehenge.com/cgi/dilbert";
my $params = [ max => 5, scary => "%&foo;%" ];
# ...
my $uri = URI->new($user_url);
$uri->query_form(@$params);
print $uri->as_string;
[download]

http://www.stonehenge.com/cgi/dilbert?max=5&scary=%25%26foo%3B%25
[download]

-- Randal L. Schwartz, Perl hacker

I failed to mention that I cannot replace existing parameters with the new one I am appending. The above code does this. So I have written the below which appears to work:

use strict;
use URI::URL;

sub addEnvVar ($$$$)
{
    my $URL = shift;
    my $name = shift;
    my $value = shift;
    my $returnRef = shift;

    # Create the URL as an object and extract already existing parameters.

    my $url = new URI::URL ($URL);
    my $qstring = $url->equery ();

    # Split the parameters up.

    my @params = split (/\&/, $qstring);

    # Split the name=value pairs up and place them in a parameter list.

    my @paramList;
    foreach my $param (@params)
    {
	my ($pname, $pvalue) = split (/\=/, $param);
	push (@paramList, $pname);
	push (@paramList, $pvalue);
    }

    # Add the new parameters to the end of the list.

    push (@paramList, $name);
    push (@paramList, $value);

    # Place the parameter list in the URL.

    $url->query_form (@paramList);

    # Get the resulting URL after appending the new variable.

    my $newURL = $url->as_string ();
    $$returnRef = $newURL;

    return 1;
}

The only minor problem I had testing this occurred when I tried to have parameters such as:
   carr%20ots=cooked
These would appear in the resulting URL as:
   carr%2520ots=cooked
But I'm not sure if its even legal to have such things in
parameters.  I think I'll stick with this for now.
Thanks a lot for your help,

Leigh

No no no. Far too much work.

use URI;

sub add_param {
  my $url = shift; # string
  my $name = shift; # string
  my $value = shift; #string

  $url = URI->new($url);
  $url->query_form($url->query_form, $name, $value);
  return $url->as_string;
}
[download]

But the problem is if you're going to call this more than once, you really ought to hoist it up to the outer level, or give it more than one pair at a time, or it will be doggy slow. </code>

-- Randal L. Schwartz, Perl hacker

Aw, darn, adding scary to the url doesn't do anything interesting :) (I was hoping for some odd easter egg, I guess. It's that season)

BTW, in case no one's mentioned this to you yet today, that dilbert page ROCKS. Thanks!
--
Mike

Yup. :)

(If you're asking what I think you're asking, that is). Name/value pairs can be added to a GET request in just the way you suggest.

hth,
andy.

Update: Of course, this won't work if the script behind the URL is expecting to receive parameters by POST rather than GET.

I'm not sure if its sufficient to simply append the string '&name=value' to a URL containing a '?', or attach '?name=value' to a URL without a '?'

alex pleiner <alex@zeitform.de>
zeitform Internet Dienste