-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[azure-storage-blob] Blob uploads and downloads give authentication error when certain characters are in the blob path #11028
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage. |
@sebastiaanzaaijer you should consider url encoding the blob names, that will get you out of this error the fastest. Let me know how it goes. |
@amishra-dev thank you very much for prompt resposnse and the suggestion. Url encoding the path does work, however then the blob gets stored in it's url encoded path rather than the intended one (see below). I'm trying to create a file structure often used for partitioned parquet files for example |
I will ask my python expert on this in a bit, but how about url encoding individual pieces of the path, is that an option? |
I believe this will still leave the url encoded piece in the blob path. Actually I suspect that url encoding could be the source of the issue, as without providing an encoded url it does encode the
|
I think it's a bug in yarl and we have created an issue in their repo |
Hi @sebastiaanzaaijer |
Would you like to confirm if you still have the problem? Thanks |
Hi, I just upgraded to azure-storage-blob==12.3.1 using pip and I still appear to have the issue. I also installed azure-core, azure-common and azure-storage-blob from master but that also didn't seem to help. |
It seems that this problem is only occuring in the aio package. When using the async version of the upload I get the following error:
|
Hi! |
Seeing this as an issue on my end too. Exclusive to the async libraries and doesn't seem to be replicated with azurite. |
Hi, It seems I found the bug and the solution - I'll send a PR in few moments. |
Hi @aviramha |
@xiafu-msft Anything I can do to speed up the process? |
Hi @aviramha We can give you a private drop so that you can install the wheel file now, does this sound good? |
I already created a wheel in my fork. Thanks anyway! |
The pr has been merged, it should be released soon #13355 |
@xiafu-msft too bad it's a different PR and didn't get a co-author 😢 |
@aviramha sorry that I should have gave you a heads up that I didn't merge your pr, and thanks for the commit! I will revert the pr partially and use your pr #13501 |
Describe the bug
An authentication error "The MAC signature found in the HTTP request '' is not the same as any computed signature. Server used following string to sign: ''" occurs when the following characters are in the blob path name:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Upload should work as expected. Creating the same folder structure in the portal or locally and then uploading using the
azcopy
tool works.Additional context
Example code, to make it run you need the following:
test
azcopy
with the following directory structure:Output:
The text was updated successfully, but these errors were encountered: