Do HTTP RANGE headers work with Azure Blob Storage Shared Access Signatures?

Question

I\'m using Azure Blob Storage to store media files and providing access to these files using Shared Access Signatures; everything is working well in this regard.

How

Answer 1

I reached out to some members of the product team and was given the following...

The 200 vs 206 is due to the presents of the "-I" flag in the curl command. This results in a HEAD request instead of a GET which is essentially as "get blob properties" call instead of a "get blob" which will cause the range header to be ignored. Also be sure to specify the version headers as "x-ms-version:2011-08-18" or later since the "startByte-" range format was only supported on that version of later.

For more information on range headers, see: http://msdn.microsoft.com/en-us/library/windowsazure/ee691967.aspx