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.

Sign up for GitHub

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

Jump to bottom

[Storage] Delete Blob API responds not include header "x-ms-delete-type-permanent", which is not aligned with rest API doc #24927

Open
blueww opened this issue Jul 21, 2023 · 1 comment
Open

[Storage] Delete Blob API responds not include header "x-ms-delete-type-permanent", which is not aligned with rest API doc #24927

blueww opened this issue Jul 21, 2023 · 1 comment
Labels
Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@blueww
Copy link
Member

blueww commented Jul 21, 2023 •
edited
Loading

In Rest API doc, Delete Blob API responds will have "x-ms-delete-type-permanent" header for version 2017-07-29 and later.
Per my test, server will also return this header after 2017-07-29, no matter the account enable/disable soft delete.

But in storage swagger, the delete blob API responds not define the header "x-ms-delete-type-permanent".
This is not aligned with rest API doc and server behavior.

Currently , Azurite (storage rest API emulator) API is generated from swagger, since in swagger Delete Blob API responds not include header "x-ms-delete-type-permanent", Azurite also won't return it.
But Azure Storage Rust SDK is expecting the x-ms-deleted-type-permanent header and fails when this header is missing in the Azureite response.
So the swagger issue caused Azure Storage Rust SDK failed on Azurite. See Azure/Azurite#2061

Please fix swagger by adding the header to make it aligned with server behavior and rest API doc.
@blueww blueww mentioned this issue Jul 21, 2023
Closed
@JackTn JackTn added Storage Storage Service (Queues, Blobs, Files) Service Attention Workflow: This issue is responsible by Azure service team. labels Jul 25, 2023
@blueww
Copy link
Member Author

blueww commented Aug 8, 2023

Hi,

Is there any update for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@blueww @JackTn