You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would appear that blobporter does not calculate MD5 and set the Content-MD5 header option when uploading to Azure.
This means two things.... first, the Content-MD5 BLOB property has no value when the file is viewed in an Azure listing.
But perhaps more importantly, second, as per the Azure Documentation "This hash is used to verify the integrity of the blob during transport. When this header is specified, the storage service checks the hash that has arrived with the one that was sent."
It is therefore a fairly important thing.
The text was updated successfully, but these errors were encountered:
Hi,
It would appear that blobporter does not calculate MD5 and set the Content-MD5 header option when uploading to Azure.
This means two things.... first, the Content-MD5 BLOB property has no value when the file is viewed in an Azure listing.
But perhaps more importantly, second, as per the Azure Documentation "This hash is used to verify the integrity of the blob during transport. When this header is specified, the storage service checks the hash that has arrived with the one that was sent."
It is therefore a fairly important thing.
The text was updated successfully, but these errors were encountered: