I have one url by which we are opening the file from azure blob storage with expiry time 30 mins but sometime after 30 minutes with st and se parameterswe are able to access the file

Ritu Gupta 0 Reputation points
2024-03-15T10:10:00.7366667+00:00

https://{{azurestorage}}.blob.core.windows.net/{{containerName}}/FileName?sv=2021-10-04&st=2024-03-14T08%3A04%3A22Z&se=2024-03-14T08%3A34%3A22Z&sr=b&sp=r&rscc=no-cache%2C+no-store%2C+must-revalidate&rscd=attachment%3Bfilename%3DAdmin_Transport_NewJoinee_Orientation_updated_May_2019_6613.pptx&rsct=application%2Fvnd.openxmlformats-officedocument.presentationml.presentation&sig=1PrpqKIGBWSGR%2Bzwz2%2FtmJzh5cTU1fYA0tjBdJt%2B0CA%3DWjgvh:ڞh{hwz{Z*']jםƲm5zi

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,412 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Sumarigo-MSFT 43,401 Reputation points Microsoft Employee
    2024-03-15T10:31:26.25+00:00

    @Ritu Gupta For better clarification of the issue: Could you please provide a screenshot of the error message? How are you attempting to access it? Could you also share a screenshot of the error and specify if it pertains to only one particular file or for all blob files?

    The URL you provided is a Shared Access Signature (SAS) URL that provides temporary access to a specific blob in your Azure Blob Storage account. The SAS URL includes a token that specifies the permissions, start time, and expiration time for the access.

    It's possible that you are able to access the file after the expiration time because the client or browser you are using has cached the file. Some clients and browsers may cache files for a period of time, even if the server has specified that the file should not be cached. To prevent caching, you can add the "Cache-Control" header to the response with a value of "no-cache, no-store, must-revalidate".

    Another possibility is that the clock on the client or server is not synchronized with the clock on the Azure Blob Storage server. If the clock on the client or server is ahead of the clock on the Azure Blob Storage server, the client or server may be able to access the file after the expiration time has passed. To prevent this, you can ensure that the clocks on all systems are synchronized using a time synchronization service.

    In any case, it's important to note that the SAS URL is intended to provide temporary access to a specific blob, and should not be used as a permanent link to the file. If you need to provide permanent access to the file, you should consider using a different method, such as a shared access policy or a stored access policy. Please let us know if you have any further queries. I’m happy to assist you further.    


    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.