Functions

Domain Name Management

After adding a domain name, you can enable or disable CDN acceleration for the domain name, or remove or review it on the CDN console.

• Adding a Domain Name: To use CDN to accelerate access to your site, add an acceleration domain name to CDN and use your site as the origin server. CDN caches origin content on PoPs so that your content loads faster.
• Enabling/Disabling CDN for a Domain Name: Temporarily disable CDN acceleration or re-enable it for your domain names.
• Deleting a Domain Name: Delete domain names in Disabled, Error, or Rejected state.
• Reviewing a Domain Name: If a domain name is banned due to ICP license expiration, apply to have it reviewed after it is re-licensed. Once the review passes, CDN unbans the domain name.
• Domain Name Quota Management: Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas limit the quantity or capacity of resources available to users.

Template Management

CDN allows you to customize templates for quick domain configuration. You can define function settings in one template and apply it to multiple domain names.

Domain Configuration Replication

You can copy the configuration of an existing domain name to other domain names.

• Copying Domain Configurations to Existing Domains: Copy the configuration of a domain name to existing domain names in a batch.
• Copying Domain Configurations to New Domains: Add new domain names with the same configuration as that of an existing domain name.

Basic Settings

When you use CDN acceleration, if the area where the origin server or end users are located changes, you can adjust basic domain name settings on CDN.

• Modifying the Service Type: Change the service type if the services of your domain name change and the current type no longer fits.
• Modifying the Service Area: If the region where your users are located changes, change the service area of your domain name to better match your services.
• Modifying Origin Server Settings: If the IP address or domain name of an origin server changes, origin server information is incorrect, or more origin servers are needed, modify the origin server settings.
• Modifying the Host Header: CDN regards an acceleration domain name as the host by default. If the domain name you want CDN to pull content is not your acceleration domain name, set a host header.
• Allowing Clients to Access CDN Using IPv6: Enable IPv6 to allow users to access CDN PoPs using IPv6.

Origin Settings

When a user requests content on an acceleration domain name, and the content is not cached on CDN PoPs, CDN PoPs will pull the content from the origin server, return it to the user, and cache it. You can set origin parameters based on your needs to speed up access.

• Origin Protocol: Configure the protocol used by CDN for origin pull.
• Origin SNI: If your origin server IP address is bound to multiple domain names and CDN visits the origin server using HTTPS, set the SNI to specify the domain to be visited by CDN during origin pull.
• Origin URL Rewrite: If the URLs of origin pull requests do not match the origin server URLs, origin pull fails. You can rewrite origin URLs to origin server URLs, improving the origin pull hit ratio.
• Advanced Origins: Configure advanced origins to allow CDN to pull content of different resource types or paths from different origin servers.
• Range Requests for Origin Pull: Allow CDN to pull large files from the origin server by range and return ranges to users, speeding up distribution and reducing bandwidth consumption.
• Redirect from Origin: If your origin server uses a 301/302 redirect, enable redirect from origin to cache the redirected resources on CDN PoPs for accelerated distribution.
• ETag Verification for Origin Pull: Enable entity tag (ETag) verification to check whether the resources are changed on the origin server after their cache on CDN PoPs expires.
• Origin Response Timeout: Adjust the origin response timeout interval based on the features and service scenarios of your origin server. The default interval is 30s.
• Origin Request Headers: Add or delete HTTP message headers in user request URLs for origin pull.
• Dynamic Content Pull Mode: By default, CDN pulls dynamic content from the origin server with the best performance. Choose to pull content from origin servers based on their weights if needed.

HTTPS Certificate Settings

HTTPS ensures secure transmission through encryption and identity authentication. CDN supports SSL certificates and other security mechanisms to secure domain names.

• Configuring an HTTPS Certificate: CDN supports HTTPS acceleration. Configure an HTTPS certificate for an acceleration domain name on the CDN console. Then clients can use HTTPS to access CDN PoPs.
• Configuring a Certificate for a Batch of Domain Names: Configure or update a certificate for multiple domain names in a batch.
• TLS Versions and Cipher Suites: Configure TLS versions and cipher suites as required.
• Force Redirect: Force clients to use HTTP or HTTPS to access CDN PoPs.
• HSTS: HTTP Strict Transport Security (HSTS) is a web security protocol promoted by Internet Engineering Task Force (IETF). Enable HSTS to force clients (such as browsers) to use HTTPS to access your server, improving access security.
• HTTP/2: Understand the background and advantages of HTTP/2.
• OCSP Stapling: When Online Certificate Status Protocol (OCSP) stapling is enabled, CDN queries and caches the status of online certificates in advance and returns the status to a browser when establishing a TLS connection with the browser. This means that the browser does not need to query the status from certificate authorities (CAs), accelerating the verification.
• QUIC: Enable the Quick UDP Internet Connections (QUIC) protocol to improve transmission security, reduce transmission and connection latency, and prevent network congestion.
• Client Certificates: Configure a client certificate to enforce mutual certificate authentication between the clients and CDN PoPs, securing website communication.

Cache Settings

CDN caches origin content on PoPs across the globe so that users can obtain content from nearby PoPs. You can modify the cache rules of resources to control the cache time to live (TTL) of resources on CDN PoPs, improving the cache hit ratio and reducing the pressure on origin servers.

• CDN PoP Cache Rules: Set a proper cache TTL for different resources on edge PoPs to improve the cache hit ratio and reduce the origin pull ratio.
• Browser Cache TTL: Set a browser cache TTL, during which users can obtain content directly from their browser cache (if available), reducing origin pulls.
• Cache TTL of Origin Response Status Codes on CDN PoPs: When a CDN PoP pulls a resource from the origin server, the origin server returns a status code. Set the cache TTL of the status code on the CDN console. When a client requests the resource again during the TTL, origin pull will not be triggered, reducing the origin pull ratio and the pressure on the origin server.
• Client Access URL Rewrite: Set access URL rewrite rules to redirect or rewrite user requests to the URLs of cached content.
• Shared Cache Groups: If different domain names point to the same resources, configure a shared cache group and set a primary domain name. Other domain names in the group share the cache of the primary domain name, improving the cache hit ratio.

Access Control

You can configure referer validation, IP address access control lists (ACLs), User-Agent ACLs, and token authentication to identify and filter out unauthorized users and improve security.

• Filtering Requests from Specific Referers: Set a policy to identify and filter out values of the Referer header in HTTP requests, controlling access sources.
• Filtering Requests from Specific IP Addresses: Set a policy to filter out requests from specific IP addresses to restrict access and prevent content theft and attacks.
• Filtering Requests from Specific User Agents: Set a policy to identify and filter visitors with specific user agents to enhance security.
• Filtering Requests from Specific Regions: Prevent users in certain geographical locations from accessing your content.
• Token Authentication: By default, the content distributed by CDN is public resources. Token authentication protects these resources from being downloaded and stolen by malicious users.
• Remote Authentication: Configure remote authentication to let CDN forward user requests to a specific authentication server and determine whether to return resources to the users based on the results returned by the authentication server.
• IP Access Frequency Control Against CC Attacks: Restrict the number of times that a single IP address requests a URL from a PoP per second to defend against CC attacks and malicious theft.

Advanced Settings

You can further configure related parameters to improve user experience and product usability.

• HTTP Response Headers from PoPs to Clients (CORS): Customize values of HTTP response headers for your website.
• Custom Error Pages: When an error is reported during user access, an error page is displayed on the user client. Customize the error page on the CDN console to optimize user experience.
• Smart Compression: When smart compression is enabled, CDN automatically compresses your static files. This saves you a lot of bandwidth by reducing file size and speeds up file transfer.
• WebSocket: If you have added whole site acceleration domain names to CDN to meet requirements such as on-screen commenting, collaborative session, market data broadcast, sports live update, online education, and IoT connectivity, configure WebSocket to implement long-term bidirectional data transmission.
• Request Rate Limiting: Limit the user request rate within a specific range to reduce costs and the risk of burst bandwidth.
• Traffic/Bandwidth Capping: Set a traffic or bandwidth cap for a domain name. When the usage reaches the cap, CDN acceleration will be disabled for the domain name, reducing high bills caused by traffic theft or attacks.
• Burst Bandwidth Alert: Set a bandwidth threshold. When the bandwidth of client requests reaches the threshold, CDN alerts you, helping you identify attacks promptly and prevent excess billing caused by bandwidth theft or attacks.

Video Seek

Allow users to seek to a certain position in a video without affecting the playback effect.

Rules Engine

The rules engine allows you to configure rules in graphical mode, which is more flexible and fine-grained. By restricting trigger conditions, you can control the resource range for the configuration to take effect, meeting requirements in various scenarios.

Cache Purge and Prefetch

Purge: Force cached content on CDN PoPs to expire. If a user requests that content, CDN has to pull fresh content from the origin server and then caches that new content.

Prefetch: Allow the origin server to proactively send the most current content to CDN PoPs. If users request the content, CDN PoPs immediately return the cached content. They do not need to pull any new content.

Analytics

CDN provides you with statistical reports. You can view and analyze data to detect exceptions and adjust services in a timely manner.

Resource Package Management

If you are billed by traffic, you can save money by buying a traffic package on the Resource Packages page. You can also view the basic package information and manage them on the Resource Packages page.

Log Management

CDN records the requests to all domain names including those deleted. If you have enabled the enterprise project function, log management is not available for these deleted domain names. You can download logs for a specific period over the past 30 days on the Logs page. Then you can analyze the access to your service resources in detail.

PoP IP Address Check

If the content shown on the access page of the acceleration domain name is abnormal, you can use the PoP IP address check tool to check whether the specified IP address is the IP address of a Huawei Cloud CDN PoP. In this way, you can know whether the abnormality is caused by the carrier network or other reasons.