Advanced Settings
For more configurations on CDN, you can understand how to configure and related precautions through this article.
Some configurations support non-standard configurations, please contact technical support for configuration.
| Features | Support |
|---|---|
| Mandatory Jump | Support |
| Custom Return Header | Support |
| Custom Response Header | Support |
| Whole Site Acceleration-QUIC | Support |
| Whole Site Acceleration-Websocket | Support |
| IPv6 | Support |
| Range Back to Source | Support |
| UA Black and White List | Support |
| Timestamp Anti-theft Chain | Support |
| Bandwidth Capping | Support |
| Single Link Speed Limit | Support |
| IP Access Frequency Limit | Support |
| Http2.0 | Support |
| HTTPS Forced Jump | Support |
| OCSP | Support |
| Intelligent Compression | Support |
Forced Jump
You can force redirect user requests to HTTPS by setting forced redirection.
Before performing this operation, please ensure that the corresponding domain has successfully configured the HTTPS certificate.
Custom Back to Source Header
By configuring the HTTP Header of back to source, you can set the back to source header information. The HTTP Header setting is implemented by setting parameters and corresponding values.
| Parameter | Description |
|---|---|
| Custom Parameters | According to your actual business needs, set parameters and values. |
Custom Response Header
By configuring the response HTTP Header, you can achieve CORS, set or designate header information included in the HTTP response header. The HTTP Header setting is implemented by setting parameters and corresponding values.
Common HTTP response header parameters are explained as follows:
| Parameter | Description |
|---|---|
| Access-Control-Allow-Origin | Specifies the allowed origin of the CORS request. When set to "*", all domains are allowed. |
| Access-Control-Allow-Methods | Specifies the allowed methods of the CORS request. Common methods are POST, GET, OPTIONS, etc. |
| Access-Control-Max-Age | Specifies the cache time of the prefetch request result of the client program for a specific resource. |
| Access-Control-Expose-Headers | Specifies the allowed fields of the CORS request. Like Cache-Control, Content-Language, Content-Type etc |
| Custom Parameters | You can also set custom parameters. |
Operating Step
1.Enter the UCDN product console [Domain Management] page, select the domain to be configured.
2.Enter the domain configuration details page, select [Domain Configuration] - [Basic Settings] - [Advanced Settings], carry out related configurations.
3.Open compulsory jump, add the back to source header, add the respond header back.
Be sure to click Confirm Configuration after the configuration modification is complete to successfully modify the configuration.
Enable mandatory jump
Add Response Header
Add Back to Source Header
Whole Site Acceleration Special Configuration
Quic
Quic protocol achieves low-latency transmission, suitable for weak network environments. If your business user scenario needs to maintain network fluency, you can choose to use the Quic protocol.
Quic protocol service is a value-added service, requiring charges for request number, for charges details please refer to Whole Site Acceleration-Request Number
Method to open: Contact the non-standard account manager for opening.
After opening, you can view the service opening status under the corresponding domain configuration.
WebSocket
WebSocket can maintain real-time communication, and does not need to continuously send requests to the server to maintain the connection. When your service needs to actively push information to the client, and has high requirements for real-time communication, it is recommended that you choose to open the WebSocket service.
Websocket service is a value-added business charge. For charges details please refer to Whole Site Acceleration WebSocket Monthly Traffic Billing
Method to open: Contact the non-standard account manager for opening.
After opening, you can view the service opening status under the corresponding domain configuration.
More Non-Standard Configurations
When you need to configure more strategies for domain, but the self-service console cannot meet, you need to contact the account manager or technical support for non-standard configuration;
The following are examples of some supported non-standard configurations. If the following configurations cannot meet your requirements, you can also contact your 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 they will be delayed on non-working days.
Protocol Category
- IPv6: Currently supports IPv6 protocol acceleration, does not support IPv6 protocol back to source.
Back to Source Category
- range to back: Segment back to source, this feature of segmented back to source is turned off by default and requires the source station to support the Range head. After this configuration is enabled, CDN will initiate Range requests to the source station (the default is to request the entire file back to source), thereby improving the efficiency of CDN content retrieval. Turning on fragment back to source may affect the back to source.
Access Control Category
-
UA Black and White List: Limit the User-Agent header of user requests, and only allow/deny requests with specified User-Agent to access CDN domain.
-
Timestamp anti-theft chain: Refer to Timestamp anti-theft chain, if there are other anti-theft chain strategies, you can also evaluate and confirm support.
-
Bandwidth Cap: By limiting the peak bandwidth of the domain, control cost or prevent attacks from affecting online services. In general, the limitation strategies are:
A. Set the peak bandwidth threshold to XXX (Mbps). For requests exceeding the threshold, limit the single connection to Y (MB/s). This restriction cannot completely limit the peak value to XXX, it will depend on the size of the single connection speed limit and the number of requests.
B. Set the peak bandwidth threshold to XXX (Mbps), and block 403 links for requests exceeding the threshold.
-
Single connection speed limit: Limit the single request to XX MB/S (KB/s, B/s can also be set; it is not recommended to set above GB/s, the effect of speed limit is not obvious).
-
IP access frequency limit: Limit the number of access times for a single IP within a unit time, and return 403 for exceeding a period of time. The configuration strategy is: if the domain/ designated directory/URL receives more than X accesses from IP in X minutes, it will be rejected (403) for subsequent access to the domain or directory or URL by the IP that reached the threshold in the next X seconds/minutes/hours
HTTPS Related
-
HTTP/2 Setting
-
HTTPS Forced Jump: HTTP request jumps to HTTPS
-
OCSP Configuration: Can improve the efficiency of TLS handshake during HTTPS request by client, and reduce user access time.
Other Configurations
- Intelligent Compression: Perform Gzip compression on static files to reduce the downstream traffic generated by requests, and speed up file transfer. The client needs to carry Accept-Encoding to make a compression request when requesting.
