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:
- Dynamic files—such as those with the extensions PHP, ASPX, ASP, JSP, DO, DWR, CGI, FCGI, ACTION, ASHX, AXD, and JSON—are not cached.
- Files with the extensions SHTML, HTML, HTM, and JS are cached for half a day (720 minutes) by default.
- All other static files are cached for one day (1,440 minutes) by default.
Create web acceleration domain names
Navigating to CDN Services
In the Microsoft Azure Management portal navigation pane, select “All services,” input “CDN,” and select “CDN profiles”
Creating CDN profiles
- In “CDN profiles,” click “Add.”
- Enter “Name,” “Subscription,” “Resource Group,” “Resource Group Location,” and “Pricing Tier,” for which the default “S1 Standard” should be selected.
- “S1 Standard” is the Standard edition of the CDN, which supports Static Content Acceleration, including Web Acceleration, Download Acceleration, and VOD Acceleration.
- “P1 Standard Plus” is the Standard Plus edition, which refers to Live Streaming Acceleration.
- “P1 Premium” is the Premium edition of the CDN. It refers to customers who requested Azure CDN to apply for a certificate on their behalf, who are still being served using this certificate, and who are still paying for the Premium edition. Support for HTTPS functions with Azure applying for certificates on the customer’s behalf will be discontinued from July 1, 2019. See Pricing Details for more information.
- Click the “Create” button.
Note: Select “S1 Standard” for the price tier, as shown in the image above. The S1 Standard includes the new “Web” acceleration type.
- After successful creation, existing records can be viewed in the list.
- Find the record that has just been created in the “CDN profiles” list and click “Name.”
- On the Overview page, click the Endpoint button
- Enter the required information on the Endpoint Create page
Note Please see Rules for Completion for required information (customer domain, ICP number, acceleration type, origin domain type, origin domain, origin host header).
In “Customer Name,” enter “Endpoint name.”
In ICP Number, enter the corresponding ICP record number for the custom domain that you entered (e.g., Jing ICP Bei XXXXXXXX Hao-X).
In the “Acceleration type” drop-down menu, choose “Web acceleration.”
Note: “Web Acceleration” does not support the “Media Service” origin domain type
In the “Origin domain type” drop-down menu, choose the corresponding service. Select one option from the list of available cloud services, storage accounts, or web apps for use in creating the Content Delivery Network endpoint.
If “Custom domain type” is selected for “Origin domain type,” please enter your origin domain address in the “origin domain” field. You can provide one or multiple origin domain IP addresses (please differentiate multiple IP addresses using a semi-colon, for example: 220.127.116.11;18.104.22.168) or an origin domain name, for example origin.chinaazuretest.com (the custom domain name can’t be the same as the origin domain name).
In “Origin host header,” enter the back-to-source 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.
Note: The specific rule is that 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 also modify this based on the actual configuration of your source station.
Click the “Add” button to create a new endpoint.
After clicking, “Creating” will be displayed in the list status.
Using the endpoint list
Endpoints list: 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 used to visit the URLs of content that is cached on the CDN
Delete endpoint Click Delete to remove suspended or unused nodes.
Manage In the endpoints list, select the endpoint you need to manage, click the Manage button, and enter the CDN portal to perform self-management.
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.