-
Notifications
You must be signed in to change notification settings - Fork 332
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
Response have metadata always when using List Containers API #2382
Comments
Thanks for raising this issue! It looks caused by :in list container API , we don't cleanup container metadata even Request doesn't have include=metadata, before return it in the request responds: Azurite/src/blob/handlers/ServiceHandler.ts Line 325 in d544d16
Would you please share you scenario impacted by this issue? Then we can evaluate the priority for this issue accordingly. Azurite welcome contribution! |
Thank you for your cheking. We cannot share detailed senario but our system use this metadata. |
…have include=metadata (issue Azure#2382)
A fix PR is already raised in #2389 |
…have include=metadata (issue Azure#2382)
The fix is merged, and normally will be include in the next Azurite release. |
Which service(blob, file, queue, table) does this issue concern?
blob service
Which version of the Azurite was used?
Azurite v3.29.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
VScode extension
What's the Node.js version?
What problem was encountered?
When we call List Containers API, response body has metadata even if request dosen't have include=metadata.
https://learn.microsoft.com/en-us/rest/api/storageservices/list-containers2?tabs=microsoft-entra-id
Steps to reproduce the issue?
Issue request and response
Request doesn't have include=metadata but response body has metadata
http://127.0.0.1:10000/devstoreaccount1/?comp=list&include=&sv=2023-01-03&ss=b&srt=sco&st=2024-03-27T14%3A25%3A53Z&se=2024-03-28T14%3A25%3A53Z&sp=rl&sig=xxxxxx
correct request and response (using product
Request doesn't have include=metadata and response body doesn't have metadata.
https://xxxxxx.blob.core.windows.net/?comp=list&include=&sv=2022-11-02&ss=b&srt=sco&sp=rwdlaciytfx&se=2024-03-28T08:51:56Z&st=2024-03-28T00:51:56Z&spr=https&sig=xxxxxx
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: