Overview

OBS Authorization

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.

Copying Domain Configurations to Existing Domains

You can copy the configuration of a domain name to existing domain names, allowing you to quickly modify domain configurations.

Copying Domain Configurations to New Domains

You can quickly add and customize domain names by copying the configuration of one domain name to one or more new domain names.

Modifying Origin Server Settings

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.

Modifying the Host Header

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.

Modifying the Service Type

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.

Modifying the Service Area

If the region where your users are located changes, you can change the service area of your domain name to better match your services.

Allowing Clients to Access CDN Using IPv6

To allow users to access CDN PoPs using IPv6, enable IPv6 on the CDN console.

Origin Protocol

You can configure the request protocol used by CDN for origin pull.

Origin SNI

If your origin server IP address is bound to multiple domains and CDN visits the origin server using HTTPS, you can set the Server Name Indication (SNI) to specify the domain to be visited by CDN.

Origin URL Rewriting

If the URLs of origin pull requests do not match the origin server URLs, you can rewrite the request URLs to improve the origin pull hit ratio.

Advanced Origins

You can configure advanced origins to allow CDN to pull content from different origin servers based on different resource types or paths.

Range Requests

If you need to improve the distribution efficiency of large files, you can enable range requests.

Redirect from Origin

Assume that 302/301 redirect is performed for your origin server address. If you do not want CDN to directly send a 302/301 redirect address to users but to instead cache the requested content and then forward the content to users, you can enable redirect from origin.

ETag Verification

If your resources on the origin server remain unchanged and you do not want CDN to pull the resources after the cache expires, you can enable ETag verification.

Origin Request Headers

You can rewrite a header in an origin pull request on the CDN console.

Origin Response Timeout

You can adjust the origin response timeout based on the features and service scenarios of your origin server.

Configuring an HTTPS Certificate

You can add a certificate for HTTPS acceleration.

HTTPS Certificate Requirements

Describes the combination and upload sequence of certificates issued by different authorities

HTTPS Certificate Format Conversion

You can convert certificates in other formats to the PEM format that CDN supports.

TLS Versions

You can enable or disable TLS versions as required.

Force Redirect

You can force redirect to HTTP or HTTPS.

HSTS

You can configure HSTS to force clients (such as browsers) to use HTTPS to access your server, improving access security.

HTTP/2

Describes the background and advantages of HTTP/2.

OCSP Stapling

If you enable this function, CDN will 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.

QUIC

You can configure the QUIC protocol to improve transmission security, reduce transmission and connection latency, and prevent network congestion.

PoP Cache Rules

• You can set the time to live (TTL) and priority for different resources to increase the hit ratio and reduce the back-to-source rate.
• You can filter URL parameters to allow CDN PoPs to ignore the parameters following a question mark (?) when caching resources, improving the cache hit ratio and speeding up distribution.
• You can set the cache TTL on CDN PoPs to be the same as that on your origin server.

Browser Cache TTL

You can set a browser cache TTL, during which users can obtain content directly from their browser cache (if available), reducing origin pulls.

Status Code Cache TTL

You can cache error status codes returned by the origin server to CDN PoPs, so CDN can return the error codes to users when they request resources. You can also set the status code cache TTL to reduce origin pull and pressure.

Access URL Rewrite

You can set access URL rewrite rules to redirect user requests to the URLs of cached content.

Shared Cache Groups

If different domain names point to the same resources, you can 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.

Referer Validation

Configure this item when you need to identify and filter visitors to restrict access.

IP ACL

Configure this item when you need to use IP address filtering to restrict access.

User-Agent ACL

Configure this item when you need to use User-Agent filtering to restrict access.

Token Authentication

Configure this item when you need to protect your website resources from being downloaded by malicious users.

Remote Authentication

Configure this item to allow CDN to forward user requests to a specific server for authentication, to prevent malicious resource download.

IP Access Frequency

You can 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.

HTTP Header Settings (Cross-origin Requests)

You can customize values of HTTP response headers for your website.

Custom Error Pages

You can customize error pages returned to user clients.

Smart Compression

You can compress static content on your websites by reducing file size. This speeds up file transfer and saves you a lot of bandwidth.

WebSocket

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, you can configure WebSocket to implement long-term bidirectional data transmission.

Request Rate Limiting

You can limit the user request rate within a specific range to reduce costs and the risk of burst bandwidth.

Usage Cap

You can 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 Seek

Configure this item to allow users to seek to a certain position in a video without affecting the playback effect.