Overview
After adding a domain name, you can customize the domain name to improve pull efficiency, website security, and cache hit ratio. Custom configuration items include OBS authorization, configuration replication, basic settings, origin settings, HTTPS settings, cache settings, access control, and advanced settings.
IP addresses belong to carriers and change irregularly. Although Huawei Cloud periodically updates the IP address library, the update may be delayed. As a result, some access control functions may occasionally block or allow requests, or client requests may not be scheduled to the optimal PoP.
OBS Authorization
This item is mandatory when the origin server is an OBS private bucket.
Item |
Description |
---|---|
If you use a Huawei Cloud OBS private bucket as the origin server, enable OBS authorization so that CDN can pull content from this bucket. |
Configuration Replication
This function is available for domain names in the Enabled, Disabled, or Rejected state.
Item |
Description |
---|---|
Copy the configuration of a domain name to existing domain names, to quickly modify domain configurations. |
|
Quickly add and customize domain names by copying the configuration of one domain name to one or more new domain names. |
Basic Settings
You can configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Item |
Description |
---|---|
If the IP address or domain name of the origin server changes, origin server information is incorrect, or a standby origin server is needed, modify the origin server settings. |
|
If the domain name you want CDN to pull content is not your acceleration domain name, set a host header. CDN regards an acceleration domain name as the host by default. |
|
If the services of your domain name change and its service type cannot meet your requirements, you can change the service type on the CDN console. |
|
If the region where your users are located changes, you can change the service area of your domain name to better match your services. |
|
To allow users to access CDN PoPs using IPv6, enable IPv6 on the CDN console. |
Origin Settings
You can configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Item |
Description |
---|---|
Configure the request protocol used by CDN for origin pull. |
|
If your origin server IP address is bound to multiple domains and CDN visits the origin server using HTTPS, set the Server Name Indication (SNI) to specify the domain to be visited by CDN. |
|
If the URLs of origin pull requests do not match the origin server URLs, rewrite the request URLs to improve the origin pull hit ratio. |
|
Configure advanced origins to allow CDN to pull content of different resource types or paths from different origin servers. |
|
Enable range requests to speed up large file distribution. |
|
Prevent CDN from directly sending a 301/302 redirect address to users when 301/302 redirect is performed for your origin server address. Force CDN to cache the requested content and then forward the content to users. |
|
If your resources on the origin server remain unchanged and you do not want CDN to pull the resources after the cache expires, enable ETag verification. |
|
Rewrite a header in an origin pull request on the CDN console. |
|
Adjust the origin response timeout based on the features and service scenarios of your origin server. |
|
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. |
HTTPS Settings
You can configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Function |
Description |
---|---|
Before configuring an SCM certificate, enable SCM authorization. |
|
Add a certificate for HTTPS acceleration. |
|
Learn how to combine and upload certificates issued by different authorities. |
|
Convert certificates in other formats to the PEM format that CDN supports. |
|
Enable or disable TLS versions as required. |
|
Force clients to request content from CDN PoPs using HTTP or HTTPS. |
|
Force clients (such as browsers) to use HTTPS to access your server, improving access security. |
|
Understand the background and advantages of HTTP/2. |
|
Allow CDN to cache the status of online certificates in advance and return the status to browsers. Browsers do not need to query the status from CAs, accelerating the verification. |
|
Configure the QUIC protocol to improve transmission security, reduce transmission and connection latency, and prevent network congestion. |
|
Configure a client certificate to enforce mutual certificate authentication between clients and CDN PoPs, securing website communication. |
Cache Settings
You can configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Item |
Description |
---|---|
|
|
Set a browser cache TTL, during which users can obtain content directly from their browser cache (if available), reducing origin pulls. |
|
Cache error status codes returned by the origin server to CDN PoPs for a specified TTL. CDN returns the error codes to users when they request resources within this TTL, reducing the origin pull ratio and origin server pressure. |
|
Set access URL rewrite rules to redirect user requests to the URLs of cached content. |
|
Configure a shared cache group with a primary domain name to share its cache with other domain names. This improves the cache hit ratio when these domain names host the same resources. |
Access Control
You can configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Item |
Description |
---|---|
Identify and filter visitors to restrict their access. |
|
Filter out requests from specific IP addresses. |
|
Filter out requests from specific user agents. |
|
Prevent users in certain geographical locations from accessing your content. |
|
Protect your website resources from being downloaded by malicious users. |
|
Allow CDN to forward user requests to a specific server for authentication, to prevent malicious resource download. |
|
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 configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Item |
Description |
---|---|
Customize values of HTTP response headers for your website. |
|
Customize error pages returned to user clients. |
|
Compress static content on your websites by reducing file size. This speeds up file transfer and saves you a lot of bandwidth. |
|
If you have enabled whole site acceleration in scenarios such as on-screen commenting, collaborative session, market data broadcast, sports live update, online education, and IoT, configure WebSocket to implement long-term bidirectional data transmission. |
|
Limit the user request rate within a specific range to reduce costs and the risk of burst bandwidth. |
|
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. |
Video Settings
You can configure the settings of a domain name that is in the Enabled or Configuring state and is not locked or banned by CDN.
Item |
Description |
---|---|
Configure this item to allow users to seek to a certain position in a video without affecting the playback effect. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot