On Thu, 3 Apr 2003, SourceForge.net wrote:

[ I'm replying to this report by mail, see the full report at this URL:
http://sourceforge.net/tracker/index.php?func=detail&aid=714667&group_id=976&atid=100976
]

> if I got e.g.a new mozilla.bz2 and than I perform:
>
> curl -z ./mozilla-source.tar.bz2 -O
> ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-source.tar.bz2
>
> mozilla-source.tar.bz2 will be transferred a second
> time. I observed this behaviour with:
> curl 7.10.4 (i686-pc-linux-gnu) libcurl/7.10.4
> OpenSSL/0.9.7 ipv6 zlib/1.1.4
> and with
> curl 7.10.2 (i686-pc-linux-gnu) libcurl/7.10.4
> OpenSSL/0.9.6 ipv6 zlib/1.1.4
>
> I supposed that it should not transferred twice. It is observed on a
> linux-2.4.20 system.

Well, it all boils down to what the FTP sever supports and responds. Can you
run a --trace-ascii and tell us exactly what kind of interaction curl does
with the FTP server in the second command invoke?

The MDTM command used for getting a time and date of a specific file over FTP
is 1. not a standard RFC959 command and 2. not very cleverly added since it
lacks time zone info.

Thus, this failure may be due to a bug in curl, or simply because the server
doesn't support the MDTM command or possibly because curl fails to do a
"good" comparison of the times on the local and remote files.

--
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/