Web acceleration

The web acceleration service is the most basic and most widely used Content Delivery Network acceleration service. It’s mainly intended to accelerate small files with low update frequencies, such as .html, .css, and .js files, images, and Flash animation.Caching these small files on Microsoft Azure Content Delivery Network edge nodes reduces access pressure on source stations and meets users’ needs for nearby website access. This improves the website access experience and helps to boost user traffic on the website.

Web acceleration Content Delivery Network nodes are suitable for use with portal websites that have large numbers of visits, such as those belonging to small, medium, or large enterprises.Other examples include government agency websites and corporate portal websites.

This article discusses the creation of web acceleration domain names. For more information about how to create Azure Content Delivery Network acceleration nodes, see Use the Azure Content Delivery Network.

Default cache rules for web acceleration

The Content Delivery Network sets default cache rules for web acceleration (see the following).You can also customize cache rules based on your needs. For more information, see the Azure Content Delivery Network Portal advanced management help file “Domain Name Management.”If the source station content is changed or updated, but the cache time-to-live (TTL) you set hasn’t expired, you can manually refresh the cache files and synchronize the updated source station content in real time. For more information, see the Azure Content Delivery Network portal advanced management help file “Cache Refresh.”

The system’s default cache rules for web acceleration:

  1. Dynamic files—such as those with the extensions PHP, ASPX, ASP, JSP, DO, DWR, CGI, FCGI, ACTION, ASHX, AXD, and JSON—are not cached.
  2. Files with the extensions SHTML, HTML, HTM, and JS are cached for half a day (720 minutes) by default.
  3. All other static files are cached for one day (1,440 minutes) by default.

Create web acceleration domain names

  1. In the navigation pane of the Azure portal, select “CDN.”
  2. In the function area, select Create New.In the Create New dialog box, select App Services > CDN > and Quick Create.

    Create New dialog box

  3. Select Web Acceleration from the Acceleration Type drop-down list.

  4. In the Origin Domain Type drop-down list, select cloud service, storage account, web app, or a customized origin domain. **Note: **“Web Acceleration” does not support the “Media Service” origin domain type.
  5. In the Origin Domain drop-down list, select one option from the list of available cloud services, storage accounts, or web apps for use in creating the Content Delivery Network endpoint.

    Origin domain option selection

    If the selected origin domain type is Customized Origin Domain, enter your own origin domain address under Origin Domain.Enter an origin domain name such as origin.chinaazuretest.com, or enter one or multiple origin domain IP addresses. Separate the multiple addresses with semicolons, for example,;

    Origin domain name

  6. In Custom Domain, enter the custom domain name you want to use, for example, cdn.chinaazuretest1.com.Custom domains support extensive domain name acceleration. Note: The custom domain name cannot be the same as the origin domain name.

  7. In Origin Host Header, enter the return-to-source access host header accepted by your source station.After you enter the custom domain, the system automatically fills in a default value based on the origin domain type that you selected.To be more specific: If your source station is on Azure, the default value is the corresponding source station address.If your source station isn’t on Azure, the default value is the custom domain that you entered. You also can modify this value based on the actual configuration of your source station.

    If the origin domain type is cloud services, the corresponding return-to-source host header is:

    Cloud services

    If the origin domain type is a custom origin domain, the corresponding return-to-source host header is:

    Custom origin domain

  8. In ICP Number, enter the corresponding ICP record number for the custom domain that you entered (for example, Jing ICP Bei XXXXXXXX Hao-X).

    ICP record number

  9. Select Create to create the new endpoint.

After you have created the endpoint, it appears in the list of subscribed endpoints.The list view shows the custom domains that are used to access cached content, as well as the origin domains. The origin domain is the original location of the content that is cached on the CDN.Custom domains are URLs that are used to access Content Delivery Network cache content.

Custom domains and origin domains

Note: Configurations created for endpoints aren’t immediately available. They must be reviewed to check that the ICP custom domain name matches the ICP number. For more information, see the second half of “Step 2: Create a new Content Delivery Network endpoint” in Use the Azure Content Delivery Network.