Share via


Specify authorization header when downloading a blob given its SAS URI

Question

Monday, August 25, 2014 5:18 PM

How to Specify authorization header when downloading a blob given its SAS URI.

All replies (3)

Monday, August 25, 2014 6:39 PM ✅Answered

Hi,
Thanks for Posting.
 Please refer to the following link and let us know if it helped
 http://stackoverflow.com/questions/11983084/delivering-and-using-an-azure-rest-api-sharedkey-for-blob-upload
Regards,
Nithin.Rathnakar


Wednesday, August 27, 2014 11:20 AM ✅Answered

Hi sir,

For your issue, I suggest you could refer to this documents:

http://msdn.microsoft.com/en-us/library/azure/dd179428.aspx

For example:

An authenticated request must include the Authorization header. If this header is not included, the request is anonymous and may only succeed against a container or blob that is marked for public access, or against a container, blob, queue, or table for which a shared access signature has been provided for delegated access.

To authenticate a request, you must sign the request with the key for the account that is making the request and pass that signature as part of the request.

The format for the Authorization header is as follows:

Authorization="[SharedKey|SharedKeyLite] <AccountName>:<Signature>"

Also, you could see this documents which explain the SAS request.

http://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-1/

and those code sample using SAS URI to download the blob:http://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-2/

Regards,

Will

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.


Monday, August 25, 2014 6:28 PM

You do not need to specify the Authorization header when the URI already contains a SAS token.