Open andreinitescu opened 11 years ago
Hi,
Thanks for posting here and we will look into this issue asap. Thanks!
Any news on this?
Hello nitescua were are planning to retire content checksum property from IAssetFile. It's duplicate usage of checksum in azure storage blob object. In WAMS user can choose to upload through sdk or using any third party tool. We can't guarantee that this property will be in sync with storage checksum value and reflect what actually stored in storage.
If you want to validate if file has been uploaded/downloaded correctly please utilize azure storage sdk by using blobProperties. CloudBlob blobRef = container.GetBlobReference(blobName); blobRef.Properties.ContentMD5
You can read more about possible checksum scenarios and find code snippets here: http://blogs.msdn.com/b/windowsazurestorage/archive/2011/02/18/windows-azure-blob-md5-overview.aspx
SDK does not set ContentChecksum on upload.
Also, documentation is misleading:
http://msdn.microsoft.com/en-us/library/microsoft.windowsazure.mediaservices.client.iassetfile.contentchecksum.aspx
"Optional. A hexadecimal number representing a MD5 (RFC 1321) message digest value. This value is set by the client or client library to serve as a validation of the successful upload of the content."
However, the property is read-only:
string ContentChecksum { get; }