Azure / Azure/Azurite

Delete Blob with blob name too long should fail

Open
#398 2 comments 0 reactions 1 assignee Claimed by @Poku8 View on GitHub
blob-storage enhancement good first issue NewArch
Dominant language
TypeScript
Stars
2.3k
Forks
393
Avg merge
1d 20h
Merged PRs (30d)
36

Description

### Which service(blob, file, queue, table) does this issue concern?
Blob
### Which version of the Azurite was used?
3.4.0
### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
### What's the Node.js version?
v11.10.0
### What problem was encountered?
When deleting a blob with a name that is too long (more than 1024 characters) using delete if not exists, I expect the operation to fail due to the bad name. Instead, the call succeeds because the HTTP response is 404. This is different than the behavior for the Azure Storage Emulator.
### Steps to reproduce the issue?
Using C++ API (or any language), call delete_blob_if_exists_async where the blob name is 1025 characters long. The call should fail, instead it reports that the blob did not exist.
### Have you found a mitigation/solution?
Disabling the test we have in our code for now.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.