You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I try to create an instance of StorageCredentials class with a SAS Token that already has api-version defined into it, I get following error:
An item with the same key has already been added.
I believe this is because UpdateQueryBuilder method doesn't check if this parameter is already defined in the query string and tries to add it nonetheless.
We should indeed update the error message to make it clearer, and we'll add that as a work item. However, the api-version parameter is owned by the component making the call, and so, we do intend to throw if that is present (the other option is to silently replace it with our own, which seems disingenuous).
pemari-msft
changed the title
Bug with StorageCredentials when using a SAS Token that already has api-version defined in it
Unclear error message when using a SAS Token that already has api-version defined in it
Apr 12, 2016
-- Mocking methods that return a sealed class Azure#335
-- Mocking CloudBlobContainer Azure#318
-- Finding it hard to mock some of the Storage classes Azure#349
-- Unclear error message when using a SAS Token that already has `api-version` defined in it Azure#259
-- ListBlobs() > Missing mandatory parameters for valid Shared Access Signature Azure#352
-- .NET Core TableEntity is throwing a storage exception on derived class properties Azure#341
-- Content-Disposition header not persisted on blob upload Azure#353
-- Request: Expose specific TableOperation properties Azure#111
-- TableOperation expose Entity Azure#358
If I try to create an instance of
StorageCredentials
class with a SAS Token that already hasapi-version
defined into it, I get following error:I believe this is because
UpdateQueryBuilder
method doesn't check if this parameter is already defined in the query string and tries to add it nonetheless.Please see this thread on StackOverflow for more details: http://stackoverflow.com/questions/36579561/how-can-i-call-new-azurestoragecontext-using-sastoken-instead-of-storageaccoun.
The text was updated successfully, but these errors were encountered: