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 email@example.com.
Jay Tanna commented
Assuming Static Website is no longer in beta since this idea was created by Abbay, I wish to report a major problem when using custom domains to link to the storage space aka Static websites. The problem is when you create a cname such as: //xxxx.domainName.com then when somebody tries to type that address in their browser's address bar they are likely to receive an error such as:
The account being accessed does not support http.
RequestId : 504f44c7-101e-003f-763a-55496a000000
TimeStamp : 2019-08-17T20:29:47.7244191Z
The file is attached for somebody to have a look at it.
However, when you type https://yourdomain.com it works. So my question is is there anyway to automatically redirect http: to https like AWS, Google Cloud and Firebase does?
+1 on the need to switch case sensitivity on or off. We're migrating apps from old platforms which are case insensitive, and the lack of this feature is forcing us to do ugly workarounds
آموزش فن بیان و مهارت های ارتباطی commented
thanks for sharing your nice and usefull information. I'm waiting for your next articles. good luck. http://www.behtarinbayan.ir
André Silva de Jesus commented
Are we limited to only one website per storage account?
Default document isn't working for directories unless that URL ends with a slash. I cannot migrate to Azure without this functionality.
Forcing HTTPS on the Standard CDN would make this totally usable. Especially since Chrome 58 flags non HTTPS websites
Dimka M commented
+1 on case sensitivity
Ryan Graham commented
+1 on Tony V's comment below regarding case sensitivity. However, I believe the web endpoint should be able to serve content regardless of of case:
should all work.
Tony Valenti commented
The static website hosting option is a great start but the case sensitivity is killing me:
index.html and Index.Html should both work!
Would you please provide some type of case-sensitivity options? Maybe "Convert all filenames to lowercase" or such?
Agree with Dimka M: static web hosting w/o custom domains and ssl is next to worthless.This was already possible.
Dimka M commented
It's great that static website hosting is now available. But seems like custom domains with custom ssl certificate are still no go (except through CDN). Come on!
Gary Forster commented
Dan Friedman commented
I don't know why they haven't updated everyone, but I already have it running. :) See https://www.youtube.com/watch?v=LFFCokEONvo
It's actually comical how bad Azure is. Thanks for the laugh guys.
Sean Feldman commented
Being the 2nd largest ask and 5 months since the last update, any updates to help people plan their work better?
Is there a timeline when this is going to be available?
Any updates on when this will be implemented? It's been almost 6 months.
Lars Simonsen commented
I was just about to move my web site to blob, then I ran into this. I guess I'll have to find a different solution.
Chris Love commented
Can't believe it has taken this long. I moved everything to AWS last year and this was a big reason why. CloudFront + S3 and Free SSL make for a great Progressive Web App platform. Glad to see you are finally making some progress. PLEASE do not make it difficult to setup. AWS is super simple.