-
Notifications
You must be signed in to change notification settings - Fork 304
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
Missing blockid in azurite signature #2375
Comments
My code, as it stands, does work with the real azure blob storage, just doesn't work with azurite |
I can't repro this issue with latest Azurite. And per Azurite code here, you can see the Uri Query parameters will be added to StringTosign. Azurite debug log in my test, you can see StringToSign contains blockid.
|
@blueww Maybe there's some parsing problem somewhere, can you try with the same block id that I used? |
Hi @hashim-hivery , I tried with the same block id you provided, it also works well.
Maybe you can share client side code you used, so we can try the same code to try to reproduce the issue? Thanks |
Hi @hashim-hivery , We found the root cause now. The block id in your URL is like: From our document, the reserved characters in query parameter value should be encoded: https://learn.microsoft.com/en-us/graph/query-parameters?tabs=http#encoding-query-parameters. Azurite implementation meets the documentation's requirement. Thanks |
Which service(blob, file, queue, table) does this issue concern?
Blob
Which version of the Azurite was used?
3.29.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
DockerHub -- mcr.microsoft.com/azure-storage/azurite@sha256:fc94c34a746aee451b7c3a46dda9d7e8844f4edaab5313862fd7ec04519fbbd0
What's the Node.js version?
v14.21.3
What problem was encountered?
Azurite seems to be omitting
blockid
query parameter from the signature calculationSteps to reproduce the issue?
The first line in the below log content obtained from debug mode is the exact failing request.
The "string to sign" used by the server,
Is different from the "string to sign" used in my code:
Log content:
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered: