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.
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
Expert Azure Architect commented
I'm going to go with Amazon since you guys don't support this. Just need a simple index.html to be supported as the default.
Any comment from Microsoft personnel?
This is an important requirement for hosting for example single page applications using blob storage.
Michael Sync commented
5 years... still under review? I need this feature as well. S3 has it. Thanks!
It's unfortunate that this feature does not exist. I'm now going to need to use AWS for all of my hosting needs due to this missing feature which is central to my business plans.
Hiromi Nagano commented
https://<account-name>.blob.core.windows.net/<container-name>/<blob-name> と指定するところを、https://<account-name>.blob.core.windows.net/ と指定するだけで、
特定の blob を参照できるようにしていただきたいです。
IIS の [既定のドキュメント] のような機能です。
ストレージアカウントに動画などを置いており、アプリケーションや ホームページ から、
「Amazon S3 での静的ウェブサイトのホスティング」
Azure Storage needs hosting a Static Website like Amazon S3.
Azure Storage Accounts require to link the full URL <https://<account-name>.blob.core.windows.net/<container-name>/<blob-name>>
in order to refer to a blob, while Amazon S3 only needs https://<account-name>.blob.core.windows.net/.
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.
Andon Petrov commented
Rackspace and Amazon have it :-(
Christopher Zenzel commented
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.
Bin Xie commented
4 years, such a dinosaur,,,
Still under review? I need this functionality now which is why I have to switch to AWS.
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.
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
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
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...
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
I love your idea. Thank you. I hope someone at Windows Azure team my get excited about it as well.
One of the most underrated features! Great job!
Andy Booth commented
Another suggestion would be when routing to a the root url, it fallbacks on whatever you specify image or .html
several others have made this suggestion too...
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.
Yingwei Yang commented
there is another feature same as this one: http://www.mygreatwindowsazureidea.com/forums/34192-windows-azure-feature-voting/suggestions/1180039-support-a-default-blob-for-blob-storage-containers?ref=title
is there a way to merge the two and add up the vote?