2009/5/13 Sai Pullabhotla <[email protected]>: > No, client does not send the checksum to the server, instead it asks the > server for the checksum of a file. The server calculates the checksum and > returns it. The client would then compare the checksum to its own calculated > checksum. > > See the link below for more information: > > http://cwiki.apache.org/FTPSERVER/draft-twine-ftpmd5-00.html > > I just want to point out that using ASCII mode to transfer files may result > in checksum mismatch depending on the client and server platforms and the > data being transferred.
Sure, I forgot to mention that. This is one of the reasons why I deeply dislike ASCII mode and avoid it altogether . > Sai Pullabhotla > www.jMethods.com > > > > On Wed, May 13, 2009 at 8:21 AM, Dan <[email protected]> wrote: > >> Could we get more information on using MD5 to ensure data integrity? >> Doesn't >> the client have to send the hash value at some point during the transfer, >> when would this be done? >> >> The way I would see it: >> >> 1. Calculate MD5 hash for the file >> 2. Upload the file >> >> When does the client send the MD5 hash to the server? >> >> Dan >> >> -----Original Message----- >> From: Niklas Gustavsson [mailto:[email protected]] >> Sent: May-13-09 6:52 AM >> To: [email protected] >> Subject: Re: STOR a temporary file >> >> On Wed, May 13, 2009 at 12:44 PM, David Latorre <[email protected]> wrote: >> > If the client renamed the file itself when the upload finished, you'd >> > be sure that it had been successfully written ( Besides, you can use >> > MD5 checks for data integrity). >> >> This is the strategy I've always used when I have automated FTP transfers >> (eg. application to application integration). I highly recommend it. If the >> server you're using doesn't support the MD5 commands, you can at least >> check >> the file length from the client. >> >> /niklas >> >> >
