We'll consider adding a SHA1 as part of the response. In the meantime, instead of downloading the whole files and creating the hash on your end, you can do a HEAD request and compare the ETag response (MD5 of the file's content).
By the way, this not only saves space but improves performance because it allows the same object to be served (and cached) even if people upload the same image over and over again.
Every upload call now also returns the etag parameter.It's the same ETag that will be returned when the resource is accessed, and can be used as a signature for the resource.
Comments
7 comments