0
votes

Based on the documentation for List Blobs for Azure Storage as mentioned here :- https://msdn.microsoft.com/en-us/library/azure/dd135734.aspx

I'm trying to list the blobs in a container using the shell script mentioned in Accessing Azure blob storage using bash, curl

The shell script works fine as it generates the correct signature.

However if there are too many blobs to list the response contains the NextMarker element.

The REST API documentation mentions that the marker value can be used in a subsequent call to request the next set of list items.

Does this marker needs to be included in the string_to_sign or would it work fine by just including it in the URL ?

1

1 Answers

2
votes

Does this marker needs to be included in the string_to_sign or would it work fine by just including it in the URL ?

Yes, this marker needs to be included in the string_to_sign.

From Authentication for the Azure Storage Services (Section: Constructing the Canonicalized Resource String):

Retrieve all query parameters on the resource URI, including the comp parameter if it exists.

Convert all parameter names to lowercase. Sort the query parameters lexicographically by parameter name, in ascending order.

URL-decode each query parameter name and value. Append each query parameter name and value to the string in the following format, making sure to include the colon (:) between the name and the value:

Since this next_marker parameter is passed as a query string parameter, it must be included in signature calculation as well.