I've found a change in behavior in Curl which may be a bug (or may be
an unfortunate design change).

I have one machine with
curl 7.9.3 (powerpc-yellowdog-linux-gnu)
and another with
curl 7.10.4 (i386-portbld-freebsd5.1)

On the 7.9.3 version, I can use curl with the -n option and a .netrc
file to retrieve a file from a password protected site, example:
curl -m 300 -nfsSo filename http://url

On the 7.10.4 version, the same request fails with message:
curl: (22) The requested file was not found

If I remove the -f (fail) option, it works. From reading some of the
entries in the mailing list archive, it looks like the fail option
causes curl to fail when it sees the HTTP 401 return code requesting
authorization. But without the -f, or with the -f on an older
version, it sends the userid/password and retrieves the file without
signalling an error,

-- 
Matt Simpson --  z/OS Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:matt_at_uky.edu>
If you ask me a question about the "mainframe", be prepared to define 
that term.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01