Membru care solicită informaţii
Last Sunday night (22-JUL-2012) between 10:30 PM - 11:59PM Central Time, my Extra Small Azure WebRole started acting a bit weird following a recent deployment. For whatever reason, my WebRole didn't want to stream several *.MP3 files that I have full legal rights to and my overall page seemed to get several "Internet Explorer cannot display the webpage" errors. Also, my access to this forum was a bit spotty.
I am on the 3 month free trial of Windows Azure and the MP3 files I speek of are being hosted locally in my WebRole instead of in Azure Blob Storage.
Is it normal for Azure to block access to MP3 files local to an XS (Extra Small) WebRole?
NOTE: A few weeks ago, I had trouble with JPEG XR (WPD) Files not getting put into my WebRole Deployment Package and I eventually wound up pushing them to the blob to solve the problem but I don't think that should be necessary:
- Editat de Shawn Eary 23 iulie 2012 11:59
If you had trouble reaching your deployment and the forum, my guess would be that there was a problem on your end.
It *may* have been a problem on my end, but I didn't have any problem with a version of my personal website on a competitor webservice and other internet connectivity seemed fine... For some reason everything is working fine now, however, this forum still gave me a bit of trouble logging in this morning.
To answer your question, no, Windows Azure doesn't know or care that your app is serving MP3 files.
Fair enough, but do you know why the VS2010 Azure SDK seems to not want include certain files during packaging? According to the StackExchange thread above, simply marking my user browse-able *.fs, *.fsi and *.wdp files with a "content" build action was not enough to get them into the package. Because I don't want to have to manually hack the package every time I deploy, I eventually decided to put the files in Azure blob storage and the problem went away; however, I think this step should not be necessary.
- Editat de Shawn Eary 23 iulie 2012 12:12