Open mikamins opened 3 weeks ago
@mikamins
Thanks for reporting this issue! We will look into how to fix it.
Azurite welcome contribution! It would be great if you could raise a PR to fix it!
The fix might can be: adding code to the following place, to report error when "x-ms-rage" end is bigger than blob length and blob length is 0 : Block & Append: https://github.com/Azure/Azurite/blob/e53428818dc418372a6885ad9c5fe8789c1061e3/src/blob/handlers/BlobHandler.ts#L1020 Page: https://github.com/Azure/Azurite/blob/e53428818dc418372a6885ad9c5fe8789c1061e3/src/blob/handlers/BlobHandler.ts#L1145
Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
v3.30.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
v20.10.0
What problem was encountered?
When downloading a byte range from a 0-sized blob, Azurite is successful (206), while a real storage account returns an error (416)
Steps to reproduce the issue?
azurite.log shows:
Azurite response
Azure response in same scenario
Have you found a mitigation/solution?
No