<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>blob storage on Michal Zolnieruk</title>
    <link>https://michalzolnieruk.io/tags/blob-storage/</link>
    <description>Recent content in blob storage on Michal Zolnieruk</description>
    <image>
      <url>https://michalzolnieruk.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://michalzolnieruk.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 26 May 2022 11:30:03 +0000</lastBuildDate><atom:link href="https://michalzolnieruk.io/tags/blob-storage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handling expired Azure Blob Storage links in a user-friendly way</title>
      <link>https://michalzolnieruk.io/posts/handling-expired-azure-blob-storage-links-in-user-friendly-way/</link>
      <pubDate>Thu, 26 May 2022 11:30:03 +0000</pubDate>
      
      <guid>https://michalzolnieruk.io/posts/handling-expired-azure-blob-storage-links-in-user-friendly-way/</guid>
      <description>📝 Use case: your app hosts files in Azure Blob Storage and users can generate expiring links to these files (using SAS tokens)
🤕 Problem: when a user opens a link with an expired SAS token, an unfriendly XML is displayed containing a technical error
😊 Solution: proxy the link with SAS token through an endpoint (Azure Function in my case), which will either redirect to the file (if the token is still valid) or show a descriptive error message</description>
    </item>
    
  </channel>
</rss>
