Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revalidate does not fix up incorrect SHA512 metadata on blob #7718

joelverhagen opened this issue Dec 2, 2019 · 0 comments


Copy link

@joelverhagen joelverhagen commented Dec 2, 2019

In DEV environment, the following package has the wrong metadata header.

(Invoke-WebRequest -Method HEAD
Key               Value
---               -----
x-ms-meta-SHA512  E590Yhwxx1ShCON7b+zUPjt3ACR997nj850yPkbFnq3JzmhW1EsrQ8eWgaYzpzUjbOFM2eYKjKTk0AvyoS2+rw==

The real hash of the content is:


The root cause is that the Azure Storage SDK takes the metadata from the destination blob as includes it in the copy request:

User-Agent: Azure-Storage/9.3.2 (.NET CLR 4.0.30319.42000; Win32NT 6.2.9200.0)
If-Match: "0x8D777789423140F"
x-ms-source-if-match: "0x8D7777973E60BAD"
x-ms-meta-SHA512: E590Yhwxx1ShCON7b+zUPjt3ACR997nj850yPkbFnq3JzmhW1EsrQ8eWgaYzpzUjbOFM2eYKjKTk0AvyoS2+rw==

As documented, this causes Azure Blob Storage to not use the source metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.