Roger, the problem is that this doesn't protect you from the biggest danger. All this does is download the file again (not desirable if it's a large file), and then compare the md5-digest of the two downloaded copies.
While this does protect you against a temporary glitch in one of the downloads, it doesn't do anything about the larger danger - that the file has become corrupted on the server. If the file on the server has been accidentally over-written, or even worse has been maliciously replaced by some virus-containing file, then this check won't save you.
It really is safer to have the md5-digest stored on the server. Ideally (for the truly cautious or paranoid), you would create the md5-digest before uploading the file, and then keep the digests on a different server, with a different username/password, so that even if the main account is compromised, the digests are still secure.
-- Alex. On 10/09/2011 20:53, Roger Eller wrote:
I am pleased as punch to report that THIS DOES WORK with an FTP path. It sure beats having to compute and store the md5digest in a separate file for each downloadable file on the server. Thanks for the suggestions. get URLencode(md5digest(URL ("ftp://user:pass@"& pFilePath))) ˜Roger _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode