Advanced Config
For more configurations about CDN, you can learn how to configure and related precautions through this article.
Some configurations are non-standard support configurations, please contact technical support if you need to configure.
| Function | Is it supported? |
|---|---|
| Forced Redirection | Supported |
| Customized Return Source Header | Supported |
| Customized Response Header | Supported |
| IPv6 | Supported |
| Range Return Source | Supported |
| UA Blacklist and Whitelist | Supported |
| Timestamp Anti-theft Chain | Supported |
| Bandwidth Capping | Supported |
| Single Link Speed Limit | Supported |
| IP Access Frequency Limit | Supported |
| Http2.0 | Supported |
| HTTPS Forced Redirection | Supported |
| OCSP | Supported |
| Intelligent Compression | Supported |
Custom Origin Header
By configuring the origin HTTP header, you can set the origin header information. The setting of the HTTP header is achieved by setting parameters and corresponding values.
| Parameter | Description |
|---|---|
| Custom parameters | Set parameters and values according to your actual business needs. |
Custom Response Header
By configuring the response HTTPHeader, you can implement cross-domain access and set or specify header information included in the HTTP response header. The setting of the HTTP header is achieved by setting parameters and corresponding values.
The common HTTP response header parameters are explained as follows:
| Parameter | Description |
|---|---|
| Access-Control-Allow-Origin | Specifies the origin of allowed cross-domain requests. When set to "*", all domains are allowed to request. |
| Access-Control-Allow-Methods | Specifies the methods of allowed cross-domain requests. Common methods include POST, GET, OPTIONS, etc. |
| Access-Control-Max-Age | Specifies the cache time for the client's pre-fetch request results for specific resources. |
| Access-Control-Expose-Headers | Specifies the fields of allowed cross-domain requests. Like Cache-Control, Content-Language, Content-Type, etc. |
| Custom parameters | You can also customize parameters. |
More Non-standard Configurations
When you need to configure more strategies for the domain but the console self-service cannot meet your needs, you need to contact the account manager or technical support for non-standard configurations.
The following are examples of some supported non-standard configurations. If the following configurations cannot meet your needs, you can also contact the account manager or technical support for non-standard evaluation and configuration.
The configuration time is related to the complexity of the requirements. Under normal circumstances, the requirements can be completed on the same working day, and non-working days will be delayed.
Protocol
- IPv6: Currently supports IPv6 protocol acceleration but does not support IPv6 protocol back to source.
Origin Class
- Range Origin: Segment Origin: The segment origin is turned off by default, and it requires the origin site to support the Range header; After enabling this configuration, CDN will initiate a range request to the origin site (the default is to request the entire file from the origin), thereby improving the efficiency of CDN content acquisition. Turning on fragment origin may affect the origin
Access Control Category
-
UA Blacklist/Whitelist: Restricts the User-Agent header of user requests, only allowing or prohibiting access to CDN domains from specified User-Agents.
-
Timestamp Anti-leech: You can refer to [Timestamp Anti-leech](../Access.md## MD5 Anti-leech). If there are other anti-leech strategies, their support can also be assessed and confirmed.
-
Bandwidth Cap: By limiting the peak bandwidth of a domain, costs can be controlled or the impact of attacks on online services can be prevented. The general restriction strategies are:
A. Set the bandwidth peak threshold to XXX (Mbps), and for requests exceeding the threshold, limit the speed of a single link to Y (MB/s). This restriction cannot completely limit the peak to the XXX value, it will accumulate based on the size of the single link speed limit and the number of requests.
B. Set the bandwidth peak threshold to XXX (Mbps), and for requests exceeding the threshold, implement a 403 ban.
-
Single Link Speed Limit: Limit the speed of a single request to XX MB/S (KB/s, B/s settings are also available; it is not recommended to set GB/s or higher, as the speed limit effect is not obvious).
-
IP Access Frequency Limit: Limit the number of accesses by a single IP within a unit of time, and if exceeded, set a time period to return 403. The configuration strategy is: if a domain, specified directory, or URL receives more than X visits from an IP within X minutes, then in the following X seconds, minutes, or hours, the IP that reaches the threshold will be denied (403). when it tries to access the domain, directory, or URL again.
HTTPS Related
-
HTTP/2 Settings
-
HTTPS Forced Redirection: HTTP requests are redirected to HTTPS
-
OCSP Configuration: Can improve the handshake efficiency of TLS during client HTTPS requests, reducing user access time.
Other Configurations
- Intelligent Compression: Gzip compresses static files to reduce the downstream traffic generated by requests and speed up file transfer rates. The client needs to carry Accept-Encoding to make a compression request.
