How can we improve Azure Storage?

Static website hosting in Azure blob storage

This would require supporting default file to render and somekind of redirect from root to a particular container.

2,077 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Abhay S shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • Hiromi Nagano commented  ·   ·  Flag as inappropriate

        https://<account-name><container-name>/<blob-name> と指定するところを、https://<account-name> と指定するだけで、
        特定の blob を参照できるようにしていただきたいです。
        IIS の [既定のドキュメント] のような機能です。

        ストレージアカウントに動画などを置いており、アプリケーションや ホームページ から、

        Amazon 様の機能としては以下の通りです。

        「Amazon S3 での静的ウェブサイトのホスティング」
        <> のような形で指定を行うと、


        Azure Storage needs hosting a Static Website like Amazon S3.

        Azure Storage Accounts require to link the full URL <https://<account-name><container-name>/<blob-name>>
        in order to refer to a blob, while Amazon S3 only needs https://<account-name>
        It's like a [default document] in IIS.

        Our customer company stores movies on the Azure Storage accounts, and link to applications and homepage, and the shorter URL is much easier to manage it.

        「Hosting a Static Website on Amazon S3」

        •This URL returns a default index document that you configured for the website.

      • Christopher Zenzel commented  ·   ·  Flag as inappropriate

        Google Drive supports default documents in shared folders via their sharing. I would use the Blob storage for development of client static sites and templates instead of Google if they allowed default documents.

      • Craig commented  ·   ·  Flag as inappropriate

        I can't believe this hasn't been addressed in 4 years!

        Static sites was one of the very first use cases for AWS S3 and Azure is still waiting.

      • Chris commented  ·   ·  Flag as inappropriate

        Long time AWS user, decided to give Azure a shot. Like it a lot, but ran into this problem. AWS allows you to return content via custom error handlers. Now I may have to go back to Amazon.

      • David Lindblad commented  ·   ·  Flag as inappropriate

        This is great idea and I really hope it'll be implemented. In addition, I believe it would be useful to be able to specify a custom 404 (and possibly a 401?!)

      • Jason Turner commented  ·   ·  Flag as inappropriate

        This would include the original URL as well so the above mentioned files can be tracked. It would also allow for timing out of SAS tokens and re-authenticating/re-issuing.

        At the moment we have to deploy a separate app to be able to do this and it's just a pain to manage...

      • Anonymous commented  ·   ·  Flag as inappropriate

        This would be great if you have links to a download that is no longer available and you want to serve something other than the ****** xml message. Would just as cool if it was a redirect handler to any url you wanted if it was coming from a browser/public

      • Anonymous commented  ·   ·  Flag as inappropriate

        I love your idea. Thank you. I hope someone at Windows Azure team my get excited about it as well.

      • Toby commented  ·   ·  Flag as inappropriate

        This is the exact problem I am facing, I would love to use azure cdn to cache dynamically created images (scaled or otherwise transformed version of an original). After the first request failing a custom 404 handler could create the image & add it for the next request.

      • Peter Reid commented  ·   ·  Flag as inappropriate

        A custom 404 handler for Blob Storage would enable me to build a "content pull" model for the CDN. A request for content from the CDN goes back to Blob storage, if its not there then a custom 404 handler will grab the content from the source content system. Very powerful feature

      • Jeff G. Young - commented  ·   ·  Flag as inappropriate

        From my forum post:

        Since there is a "trick" to create blobs in the root of a storage account ("$root"), I was hoping there was a trick to create a default document for a blob container. Maybe "$default" or something like that?

        I would like to serve requests at the root of the storage account with a particular blob. So, if I used a CNAME record to map to, then requests to could retrieve this default blob.

        The scenario I want to enable is CDN caching of the first page hit for a site, which will be a very small bootstrapping page that puts up a loading indicator then pulls more CDN cached data as well as live data from my windows azure web role. But I need to support alone, not just

        And of course, using any kind of redirect to get to would seriously undermine the value of this scenario.

        If this feature doesn't exist, I suggest it should.

        Jeff G. Young @jeffcodes

      • moorster commented  ·   ·  Flag as inappropriate

        I agree. S3 just added support for root documents. We need it too! I need to be able to put index.html (or index.htm) on my site and avoid having to type it into the URL.

      Feedback and Knowledge Base