azure-cdn

问题 I am trying to update 2 rules in Azure CDN Management (Verizon) Recently they update to V4 and the prefix source is no longer coming on the field Rule 1 -> If http redirect to https Rule 2 -> If url is empty (only root) serve default document index.html The new rules engine is unable to identify the Source I already try Leaving it blank www.[mydomain].com [mydomain].com / The old version had the CDN Verizon id hardcoded on the field, maybe this what is missing? how can I find this? 回答1:

问题 I have succesfully set up a static website on Azure Blob storage using the $web container as advised within the Microsoft documentation. In addition, I have defined index.html for both the 'Index Document Name' and the 'Error Document Name'. This is because I want my JavaScript application to handle the 404 responses. However, when looking at the network tab in Chrome, I can see that a 404 is being thrown for the URL that I am requesting, despite the page actually working. My theory is as

问题 Context I've been struggling with the following problem for the last few days and due to the very nature of a CDN and the manual review of each new rule, it takes me each time up to 4h to deploy a new rule. As described in the following topic, I currently have my Angular application deployed to a storage account which has a single blob container called cdn Within the root of this blob container , the whole dist folder from my angular project has been copied via my CI setup. The CDN profile

问题 Context I've been struggling with the following problem for the last few days and due to the very nature of a CDN and the manual review of each new rule, it takes me each time up to 4h to deploy a new rule. As described in the following topic, I currently have my Angular application deployed to a storage account which has a single blob container called cdn Within the root of this blob container , the whole dist folder from my angular project has been copied via my CI setup. The CDN profile

问题 I use CDN for my cloud services in Azure, but fonts (*.woff) does not work! When i use just iis for static files i solve this problem like <staticContent> <mimeMap fileExtension=".woff" mimeType="application/x-font-woff" /> </staticContent> (http://stackoverflow.com/questions/3594823/mime-type-for-woff-fonts) But how i can do it in microsoft azure cdn? 回答1: Its cross-domain so you also need to add: <system.webServer> <httpProtocol> <customHeaders> <add name="Access-Control-Allow-Origin" value

问题 We have a web app that runs on Azure App Service and it has its own domain i.e. myapp.com We now want to host all static files such as images, css and js files through Azure CDN to improve responsiveness of the app. We'll be storing all these files in our Azure storage and we've created two containers i.e. "images" and "files" containers. We also want to use our own custom domain and I'd like the URLs to be: https://cdn.myapp.com/images for images and https://cdn.myapp.com/files for all other

问题 I am using Premium Verizon CDN, met with a peculiar case where-in the endpoint host name is HTTPs enabled (CDN provided certificate) but Azure Portal shows that it is still at Domain Name Validation. Enabling HTTPs was initiated on 1st Feb and from 2nd Feb the endpoint has a valid SSL certificate, but for some reason the Azure portal has not updated yet & still stuck at domain validation (its been close to 3 days now). Has anyone encountered such a behavior yet? 回答1: Possibly, this is the

问题 Azure Data lake Storage hostname is not shown in the dropdown menu when I am trying to configure Azure CDN with Origin Type as Storage 回答1: The origin Type of Azure CDN profile is：Storage, Web App, Cloud Service &Custom Origin. There is no Azure Data Lake at currently. And Azure Data Lake Store is still in preview. If you have any feature request, please submit in Azure feedback forum. 来源： https://stackoverflow.com/questions/39761466/azure-cdn-origin-hostname-not-shown-when-origin-type

问题 I have an Azure CDN (Verizon, premium) connected to blob storage. I have 2 rules in place based on step 6 in this tutorial. The rules are designed to force the CDN to serve "index.html" when the root of the CDN is called. They may or may not be relevant to the issue, but they are described in Step 6 as follows: Make sure the dropdown says “IF” and “Always” click on “+” button next to “Features” twice. set the two newly-created dropdowns to “URL Rewrite” set the all the sources and destination

问题 We are trying to enable HTTP compression (gzip) and HTTP 304 Caching via ETags on Azure CDN. We already discovered an issue with enabling Azure CDN Compression, but now we can't get compression and ETag caching (304s) working simultaneously. This issue has been posted to Azure forums here. Here is an example of the compressed, but not HTTP cacheable (304) link: https://xxxx.vo.msecnd.net/resourceManager.axd?token=HL80vX5hf3lIAAA&group=core.js Here is an example of the cacheable (304), but not