Hi Albert,

the problem is not with 'unsafe characters' but rather caused by the fact
that the characters '[', ']', '{', '}' have a special meaning in the curl
command line - they are used to express ranges of URLs to be downloaded,
e.g. http://www.wherever.com/page[1-9].html will download pages #1 through
#9. The precise error message for your example should read "empty range
specification".
Just go ahead and escape the special characters (.../?foo\[\]=1) and it'll
all work as expected.

Cheers,
    Joern

> -----Ursprüngliche Nachricht-----
> Von: Albert Chin-A-Young [mailto:china_at_thewrittenword.com]
> Gesendet: Samstag, 26. August 2000 17:20
> An: curl_at_contactor.se
> Betreff: encoding unsafe characters (with 7.1.1)
>
>
> % curl 'http://www.yahoo.com/?foo[]=1'
> error: illegal character in range specification at pos 27
>
> Shouldn't curl automatically encode unsafe characters? Wget and lftp
> currently do.
>
> --
> albert chin (china_at_thewrittenword.com)
>
Received on 2000-08-28