On Tue, 14 Apr 2009, Angus March wrote:

> I'm having 2 problems where the implementation version of libcurl keeps
> giving me these "URL using bad/illegal format or missing URL" errors when
> there shouldn't be anything wrong w/the URLs.

I'd suspect your code...

> Another problem is that when I can get these binary files to transfer, they
> go as ASCII, and I don't know how to get them to transfer binary.

libcurl defaults to binary so something is weird.

> The implementation machine is a 32-bit Suse Enterprise 10, which uses
> libcurl 7.15.1 . That's a little older than what I have on the development
> machine (7.19.0 on an AMD64 running Suse 11.1) and the problem doesn't occur
> on that system.

Then I suggest you upgrade libcurl on the "implementation machine" and you're
done! I'm not very interested in chasing bugs or problems that no longer
appear...

> char c[1000];
> verify(curl_easy_getinfo(curl,
> CURLINFO_EFFECTIVE_URL, c) == CURLE_OK);

This code is plain wrong. Re-read the man page!

-- 
  / daniel.haxx.se