blocks|key|861394|text|几天前我也遇到了同样的问题。我实际上期望存储服务在SAS令牌过期时返回403错误代码，但存储服务返回404错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|861395|鉴于我们没有任何其他选择，您这样做是唯一可行的方法，但它仍然是不正确的，因为如果存储帐户中不存在blob，您可能会得到404错误。|861396|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I also ran into the same issue a few days back. I was actually expecting storage service to return a 403 error code when the SAS token has expired but storage service returns 404 error.

Given that we don't have any other option, the way you're doing it is the only viable way but it is still not correct because you could get 404 error if the blob is not present in the storage account.

blocks|key|861463|text|也许你可以从生成的SAS中解析"se“参数，这意味着过期时间，例如"se=2013-04-30T02%253A23%253A26Z”。但是，由于服务器时间可能与客户端时间不同，因此解决方案可能不稳定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|861464|http://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-1/|offset|length|861465|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2U|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Maybe you can parse "se" argument from the generated SAS, which means expiry time, e.g. "se=2013-04-30T02%3A23%3A26Z". However, since the server time might not be the same as client time, the solution may be unstable.

<a href="http://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-1/" rel="nofollow">http://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-1/</a>

blocks|key|4317071|text|我尝试运行与您的代码非常相似的代码，我得到了一个403错误，这实际上是本例中所期望的。根据你的问题，我不确定403比404对你更有帮助。下面是在控制台应用程序中运行的代码，它返回403：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4317072|class+Program
{
++++static+void+Main(string[]+args)
++++{
++++++++string+blobUrl+=+CreateSAS();
++++++++CheckSAS(blobUrl);

++++++++Console.ReadLine();
++++}

++++//This+method+returns+a+reference+to+the+blob+with+the+SAS,+and+attempts+to+read+it.
++++static+void+CheckSAS(string+blobUrl)
++++{
++++++++CloudBlockBlob+blob+=+new+CloudBlockBlob(new+Uri(blobUrl));

++++++++//If+the+DownloadText()+method+is+run+within+the+two+minute+period+that+the+SAS+is+valid,+it+succeeds.
++++++++//If+it+is+run+after+the+SAS+has+expired,+it+returns+a+403+error.
++++++++//Sleep+for+3+minutes+to+trigger+the+error.
++++++++System.Threading.Thread.Sleep(180000);
++++++++Console.WriteLine(blob.DownloadText());
++++}

++++//This+method+creates+the+SAS+on+the+blob.
++++static+string+CreateSAS()
++++{
++++++++string+containerName+=+"forum-test";
++++++++string+blobName+=+"blobname";
++++++++string+blobUrl+=+"";

++++++++CloudStorageAccount+storageAccount+=+CloudStorageAccount.Parse(CloudConfigurationManager.GetSetting("StorageConnectionString"));
++++++++CloudBlobClient+blobClient+=+storageAccount.CreateCloudBlobClient();
++++++++CloudBlobContainer+container+=+blobClient.GetContainerReference(containerName);
++++++++container.CreateIfNotExists();

++++++++CloudBlockBlob+blockBlob+=+container.GetBlockBlobReference(blobName+%2B+DateTime.Now.Ticks);
++++++++blockBlob.UploadText("Blob+for+forum+test");

++++++++//Create+an+ad-hoc+Shared+Access+Policy+with+read+permissions+which+will+expire+in+2+hours
++++++++SharedAccessBlobPolicy+policy+=+new+SharedAccessBlobPolicy()
++++++++{
++++++++++++Permissions+=+SharedAccessBlobPermissions.Read,
++++++++++++SharedAccessExpiryTime+=+DateTime.UtcNow.AddMinutes(2),
++++++++};

++++++++SharedAccessBlobHeaders+headers+=+new+SharedAccessBlobHeaders()
++++++++{
++++++++++++ContentDisposition+=+string.Format("attachment;filename=\"{0}\"",+blobName),
++++++++};
++++++++var+sasToken+=+blockBlob.GetSharedAccessSignature(policy,+headers);
++++++++blobUrl+=+blockBlob.Uri.AbsoluteUri+%2B+sasToken;

++++++++return+blobUrl;
++++}
}|code-block|syntax|javascript|4317073|在某些情况下，SAS故障会返回404，这可能会给使用SAS排除故障的操作带来问题。Azure存储团队意识到了这个问题，在未来的版本中，SAS故障可能会返回403。有关404错误的故障排除帮助，请参阅http://azure.microsoft.com/en-us/documentation/articles/storage-monitoring-diagnosing-troubleshooting/#SAS-authorization-issue。|offset|length|4317074|entityMap|0|LINK|mutability|MUTABLE|url|http://azure.microsoft.com/en-us/documentation/articles/storage-monitoring-diagnosing-troubleshooting/#SAS-authorization-issue^0|0|0|2R|3I|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I tried running code very similar to yours, and I am getting a 403 error, which is actually what is expected in this case. Based on your question, I am not sure whether the 403 is more helpful to you than the 404. Here is code running in a console application that returns a 403:

<pre><code>class Program
{
 static void Main(string[] args)
 {
 string blobUrl = CreateSAS();
 CheckSAS(blobUrl);

 Console.ReadLine();
 }

 //This method returns a reference to the blob with the SAS, and attempts to read it.
 static void CheckSAS(string blobUrl)
 {
 CloudBlockBlob blob = new CloudBlockBlob(new Uri(blobUrl));

 //If the DownloadText() method is run within the two minute period that the SAS is valid, it succeeds.
 //If it is run after the SAS has expired, it returns a 403 error.
 //Sleep for 3 minutes to trigger the error.
 System.Threading.Thread.Sleep(180000);
 Console.WriteLine(blob.DownloadText());
 }

 //This method creates the SAS on the blob.
 static string CreateSAS()
 {
 string containerName = "forum-test";
 string blobName = "blobname";
 string blobUrl = "";

 CloudStorageAccount storageAccount = CloudStorageAccount.Parse(CloudConfigurationManager.GetSetting("StorageConnectionString"));
 CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();
 CloudBlobContainer container = blobClient.GetContainerReference(containerName);
 container.CreateIfNotExists();

 CloudBlockBlob blockBlob = container.GetBlockBlobReference(blobName + DateTime.Now.Ticks);
 blockBlob.UploadText("Blob for forum test");

 //Create an ad-hoc Shared Access Policy with read permissions which will expire in 2 hours
 SharedAccessBlobPolicy policy = new SharedAccessBlobPolicy()
 {
 Permissions = SharedAccessBlobPermissions.Read,
 SharedAccessExpiryTime = DateTime.UtcNow.AddMinutes(2),
 };

 SharedAccessBlobHeaders headers = new SharedAccessBlobHeaders()
 {
 ContentDisposition = string.Format("attachment;filename=\"{0}\"", blobName),
 };
 var sasToken = blockBlob.GetSharedAccessSignature(policy, headers);
 blobUrl = blockBlob.Uri.AbsoluteUri + sasToken;

 return blobUrl;
 }
}
</code></pre>

There are cases in which SAS failures do return a 404, which can create problems for troubleshooting operations using SAS. The Azure Storage team is aware of this issue and in future releases SAS failures may return a 403 instead. For help troubleshooting a 404 error, see <a href="http://azure.microsoft.com/en-us/documentation/articles/storage-monitoring-diagnosing-troubleshooting/#SAS-authorization-issue" rel="nofollow">http://azure.microsoft.com/en-us/documentation/articles/storage-monitoring-diagnosing-troubleshooting/#SAS-authorization-issue</a>.

blocks|key|2850028|text|您正在为SharedAccessExpiryTime使用UTC时间(请参阅https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1#parameters-common-to-account-sas-and-service-sas-tokens中的“过期时间”)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2850029|然后，在令牌中的se声明下注册过期时间，在实际使用令牌之前，可以根据客户端的当前UTC时间检查该令牌的值。这样，您就不必额外调用Blob存储来确定令牌是否已过期。|2850030|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1#parameters-common-to-account-sas-and-service-sas-tokens^0|4|M|11|4B|0|0|8|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

You're using UTC time for <code>SharedAccessExpiryTime</code> (see "Expiry Time" in <a href="https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1#parameters-common-to-account-sas-and-service-sas-tokens" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1#parameters-common-to-account-sas-and-service-sas-tokens</a>).

The expiry time then is registered under the <code>se</code> claim in the token the value of which can be checked against current UTC time on the client side before actually using the token. This way you'd save yourself from making an extra call to the Blob storage only to find out whether the token is expired.

i have written this below code to get the blob url with cache expiry token, actually have set 2 hours to expire the blob url,

<pre><code> CloudStorageAccount storageAccount = CloudStorageAccount.Parse(CloudConfigurationManager.GetSetting("StorageConnectionString"));
 CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();
 CloudBlobContainer container = blobClient.GetContainerReference(containerName);
 CloudBlockBlob blockBlob = container.GetBlockBlobReference("blobname");
 //Create an ad-hoc Shared Access Policy with read permissions which will expire in 2 hours
 SharedAccessBlobPolicy policy = new SharedAccessBlobPolicy()
 {
 Permissions = SharedAccessBlobPermissions.Read,
 SharedAccessExpiryTime = DateTime.UtcNow.AddHours(2),
 };

 SharedAccessBlobHeaders headers = new SharedAccessBlobHeaders()
 {
 ContentDisposition = string.Format("attachment;filename=\"{0}\"", "blobname"),
 };
 var sasToken = blockBlob.GetSharedAccessSignature(policy, headers);
 blobUrl = blockBlob.Uri.AbsoluteUri + sasToken;
</code></pre>

using this above code i get the blob url with valid expiry token, now i want to check blob url is valid or not in one client application.
I tried web request and http client approach by passing the URL and get the response status code. if the response code is 404 then I assuming the URL is expired if not the URL is still valid,but this approach taking more time.

Please suggest me any other way.

How do i find bloburl with shared access token expired?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我已经写了下面的代码来获得带有缓存过期令牌的blob url，实际上已经设置了2小时来过期blob url，            CloudStorageAccount storageAccount = CloudStorageAccount.Parse(CloudConfigurationManager.GetSe...

问如何查找共享访问令牌过期的bloburl？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何查找共享访问令牌过期的bloburl？EN