in reply to how to url encode at OS level?

The OS and the shell don't know about "url-encoding", but they (like Perl) know about "quoting", except that the quoting rules differ between the shells. Perl's system function can (try to) circumvent the shell if you give it a list of strings instead of one string:

system 'start', 'http://www.foo.com/cgi-bin/foo.cgi?a=2&b=3';

Alternatively, you can do the shell quoting yourself:

system 'start "http://www.foo.com/cgi-bin/foo.cgi?a=2&b=3"';

Replies are listed 'Best First'.
Re^2: how to url encode at OS level?
by redss (Monk) on Jul 19, 2006 at 14:19 UTC
    thanks for the suggestions. Does it work for you? Unfortunately on my system, the first suggestion still results in the subsequent args getting filtered out and the browser only sees the first parameter. Your 2nd suggestion effectively resulted in only 2nd cmd window being displayed.

      Does it work for you? When I type the following into a command prompt:

      Q:\>start "http://www.foo.com/cgi-bin/foo.cgi?a=2&b=3"

      a new console window opens, with the title http://www.foo.com/cgi-bin/foo.cgi?a=2&b=3 gets opened. This is as designed, as the start command often likely interprets the first argument as the console window title (see the help text as output by help start). OK, I admit, I didn't test it, but you should make sure what you attempt will also give the desired result.