Azure / Azure/Azurite

Azurite doesn't check if the parameter sequenceNumber is valid when use Update Sequence Number operation on page blob.

Open
#643 2 comments 0 reactions 1 assignee Claimed by @blueww View on GitHub
alignment blob-storage bug NewArch
Dominant language
TypeScript
Stars
2.3k
Forks
393
Avg merge
1d 20h
Merged PRs (30d)
36

Description

**Error Description:**
In Azure, it will return error "InvalidHeaderValue" when use Update Sequence Number operation with invalid sequenceNumber.
But in Azurite, it will update sequence number successfully in this case.
Azure error is shown as following:
![Screenshot 2020-11-19 100728](https://user-images.githubusercontent.com/20970631/100212439-4b281180-2f48-11eb-8037-e096ba924e86.png)

**To Reproduce**
The demo code is shown as following:
```
import {
BlobServiceClient
} from "@azure/storage-blob";
import * as assert from "assert"

async function main(){
const blobServiceClient = await BlobServiceClient.fromConnectionString("");
const containerClient=await blobServiceClient.getContainerClient("");
const pageBlobClient = containerClient.getPageBlobClient("");
try{
await pageBlobClient.updateSequenceNumber('update',1);
}catch(err){
console.log(err);
assert.ok((err as any).response.parsedBody.Code === "InvalidHeaderValue");
}
}

main();
```

**Expected Behavior**
When use Update Sequence Number operation with invalid sequenceNumber, Azurite return error "InvalidHeaderValue".

@jongio for notification.

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.