StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>A few things I noticed:</p> <ol> <li>You mentioned that you're using SDK 2.0 however I think you're not using the latest storage client library (2.0.6). From your code, it seems you're still using old storage client library (1.8). Can you please check in your code if you're referencing <code>Microsoft.WindowsAzure.StorageClient</code> or <code>Microsoft.WindowsAzure.Storage</code>. If it is former, then you're using old library.</li> <li>If you're using old storage client library, then please note that with old storage client library which makes use of old Storage REST API, for anonymous SAS tokens (i.e. tokens without container access policy) you can't specify an expiration time more than 1 hour from current time (in UTC of course). If I try to use your URL, I get the following error message (under <code>AuthenticationErrorDetail</code> node:</li> </ol> <blockquote> <p>Access without signed identifier cannot have time window more than 1 hour</p> </blockquote> <p>Can you try by creating a SAS token which is valid for less than 1 hour? E.g.</p> <pre><code>var sasToken = blob.GetSharedAccessSignature(new SharedAccessPolicy { Permissions = SharedAccessPermission.Read, SharedAccessExpiryTime = DateTime.UtcNow + TimeSpan.FromMinutes(30) } ); </code></pre> <p>If you continue to want to use the older storage client library, you have a few choices:</p> <ol> <li>Create a SAS Token which is valid for less than an hour as explained above.</li> <li>Use a container level access policy to create a SAS token. With a container level access policy, you will be able to define SAS tokens which have an expiry date more than 1 hour. For more on this, please click here: <a href="http://msdn.microsoft.com/en-us/library/windowsazure/ee393341.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/windowsazure/ee393341.aspx</a></li> </ol> <p>If you use the new storage client library, you would be able to define longer duration token without using a container access policy. However there are a lot of differences between the two versions of the library and migration from older to newer version is not trivial. I wrote a blog post some days ago about migrating code from older version to newer version. You can read it here: <a href="http://gauravmantri.com/tag/storage-client-library/" rel="nofollow">http://gauravmantri.com/tag/storage-client-library/</a>. Lastly, I wrote a blog post on SAS, which you can read here: <a href="http://gauravmantri.com/2013/02/13/revisiting-windows-azure-shared-access-signature/" rel="nofollow">http://gauravmantri.com/2013/02/13/revisiting-windows-azure-shared-access-signature/</a>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload