azure-cdn

Azure CDN rules engine to add default document EXCEPT for files requested by the site

点点圈 提交于 2019-12-05 08:51:23
I am using Azure Verizon CDN to publish my web application (an SPA) from Blob storage. I've successfully set up a custom domain and SSL. I've added a rewrite rule in the CDN to redirect to the default document index.html. Basically, this takes the incoming request and inserts "index.html" between the URL path and any query strings. So mydomain.com/startup goes to mydomain.com/startup/index.html mydomain.com/homepage goes to mydomain.com/homepage/index.html and mydomain.com/showuser/?userId=xxxxx goes to mydomain.com/showuser/index.html/?userid=xxxxx Which all seems to work well. Existing rule

azure cdn purge not refreshing cached content

*爱你&永不变心* 提交于 2019-12-04 07:44:43
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 dropdowns to the endpoint you created (the value with the endpoint name) for the first source pattern

Azure CDN - Enabling HTTP 304 Caching with ETag - Hosted Web Role

折月煮酒 提交于 2019-12-03 14:55:23
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 compressible (gzip) link: https://xxxx.vo.msecnd.net/resourceManager.axd?token=HL80vX5hf3lIAAA

Using Azure CDN with Shared Access Signatures

余生长醉 提交于 2019-12-03 13:12:14
问题 Im trying to incorporate Azure to store the majority of my files for an application. I want to upload these files to a private container and private blob in azure, and have those uploads copied through the Azure CDN to all of the other nodes (still as private containers and blobs). I then want my application to make a request to a stored blob, and give me the shared access signature link to the blob for a period of time. However, I want the link generated to be given for the closest

Forcing HTTPS with Azure CDN

橙三吉。 提交于 2019-12-03 05:39:41
I’m using Azure CDN in front of a Storage Account. I’m wanting to serve everything via HTTPS only, so I’ve setup HTTPS on the custom domain and created a URL rewrite: But the problem is that I end up at a URL like this: https://the-custom-domain/website/17/index.html The website/17/index.html is the root content within the Storage Account, but I don’t know why it’s appending the container path before the filename. There’s also rewrite rule for static files ( https://blog.lifeishao.com/2017/05/24/serving-your-static-sites-with-azure-blob-and-cdn ). Any idea what’s wrong with the URL rewrite?

Using Azure CDN with Shared Access Signatures

一笑奈何 提交于 2019-12-03 03:21:54
Im trying to incorporate Azure to store the majority of my files for an application. I want to upload these files to a private container and private blob in azure, and have those uploads copied through the Azure CDN to all of the other nodes (still as private containers and blobs). I then want my application to make a request to a stored blob, and give me the shared access signature link to the blob for a period of time. However, I want the link generated to be given for the closest datacenter to the user. I will have the SAS be generated each time a blob is needed, but I need to be able to

Why isn't 'Vary: Origin' response set on a CORS miss?

与世无争的帅哥 提交于 2019-11-29 23:07:38
When making a CORS request, if the requested Origin is on the list of allowed origins, the response contains both the Access-Control-Allow-Origin header, and the Vary: Origin header. The Vary: Origin telling onward CDNs etc that the response was negotiated based on the requestors Origin header value. The issue is (and I've tested the leading CDN providers), is that if the requestor doesn't provide a Origin header in their request, or an Origin value that is not one of the allowed ones, the response does not include the Vary: Origin in the response. Should a CDN preforming CORS always respond

Azure, best way to store and deploy static content (e.g. images/css)?

試著忘記壹切 提交于 2019-11-29 21:07:35
We're about to deploy our .NET web application to an Azure Web Role. I'm just wondering how others have handled their static content, specifically images and css? At the moment our application package is about 25mb but 18mb of that is derived purely from images, things like navigation buttons, icons and template components that rarely ever get updated. Would it be wise to partition this out of the deployment package and move it to blob storage? I have a few doubts about this approach that I'm wondering are valid... 80% of our site runs in a HTTPS environment. Will accessing images in a blob

How to create CDN in Windows Azure

允我心安 提交于 2019-11-29 11:32:47
I'm trying to deliver a file via CDN.I created a Blob and uploaded the file to it. Now i want to use a CDN to deliver it as per Azure docs here http://www.windowsazure.com/en-us/manage/services/other/cdn/ In the Windows Azure Management Portal, in the navigation pane, click CDN. On the ribbon, click New. In the New dialog, select App Services, then CDN, then Quick Create. The problem is in my account there is nothing called App Services How am i supposed to create the CDN? If you are new to Azure (you created your account recently) you will not see CDN in the portal. Currently CDN is only

Why isn't 'Vary: Origin' response set on a CORS miss?

雨燕双飞 提交于 2019-11-28 20:19:17
问题 When making a CORS request, if the requested Origin is on the list of allowed origins, the response contains both the Access-Control-Allow-Origin header, and the Vary: Origin header. The Vary: Origin telling onward CDNs etc that the response was negotiated based on the requestors Origin header value. The issue is (and I've tested the leading CDN providers), is that if the requestor doesn't provide a Origin header in their request, or an Origin value that is not one of the allowed ones, the