"Incorrect padding" while attempting to check if blob exists #36379
Labels
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
Service Attention
Workflow: This issue is responsible by Azure service team.
Storage
Storage Service (Queues, Blobs, Files)
azure-storage-blob
Describe the bug
A call to
BlobClient.exists
fails after a huge delay with:To Reproduce
Steps to reproduce the behavior:
"a"
.Expected behavior
The error here needs to help me understand what's wrong; base64 padding has "nothing" to do with the API call here, and I had no idea at first what I'd done wrong, as I thought I had supplied a valid key.
The long timeout is equally weird; this should abort immediately … no?
The signature generation scheme here is to a user of the API an internal detail. I'm "lucky" in the sense that I've implemented it by hand before & know how it works (and that's what nudged me towards "maybe the key I supplied wasn't right?"), but a user who isn't familiar with how the signature scheme on the underlying API requests work is going to just be perplexed by this.
Screenshots
N/A
Additional context
I suspect this was previously reported here: #35010
The text was updated successfully, but these errors were encountered: