On Sun, 17 Oct 2004, nelson wrote:

> So, although that URL is probably no rtf compliant, I think libCURL should
> modify it correctly, for the goodness of end users, like wget does...

I strongly disagree. It goes against the whole design principle of libcurl.

I WANT you to be able to pass whatever URLs you want, as long as they are
syntactically correct.

For example, you can use curl to test how the server deals with excessive
amounts of ../ like this. Apparently you can't do that with wget since it
tries to be smart about them. It is not "better than" curl in my view. It is
just different.

I suggest you provide a good URL to get good data.

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html