Validate proposed Blob and Container lease IDs - #2812
Akanksha Jain (jainakanksha-msft) with Copilot wants to merge 8 commits into
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: jainakanksha-msft <181211853+jainakanksha-msft@users.noreply.github.com>
Co-authored-by: jainakanksha-msft <181211853+jainakanksha-msft@users.noreply.github.com>
Co-authored-by: jainakanksha-msft <181211853+jainakanksha-msft@users.noreply.github.com>
Co-authored-by: jainakanksha-msft <181211853+jainakanksha-msft@users.noreply.github.com>
|
Copilot Please address all remaining review feedback on this PR. At minimum: (1) replace every existing proposed-lease fixture using |
Co-authored-by: jainakanksha-msft <181211853+jainakanksha-msft@users.noreply.github.com>
Co-authored-by: jainakanksha-msft <181211853+jainakanksha-msft@users.noreply.github.com>
Addressed in Results:
|


Azurite accepted malformed
x-ms-proposed-lease-idvalues on Blob and Container acquire/change lease paths. Azure Storage rejects these withInvalidHeaderValueand accepts the documented GUID string formats, including X-format GUIDs.acquireLeaseandchangeLeasehandlers.InvalidHeaderValuewithHeaderName/HeaderValuedetails for malformed proposed lease IDs.Coverage
Release notes
Original prompt