Yes. Tencent has built nodes for over a decade. Tencent Cloud CDN offers over 1,000 overseas nodes in more than 50 countries and regions to help your business go global seamlessly.
No. To achieve a better acceleration result, however, you are recommended to assign static and dynamic files to different domain names and only accelerate static resources.
Yes. If cross-origin access is needed for your website, simply configure the
Access-Control-Allow-Origin field on your website or configure cross-origin headers for your domain name in the CDN Console. For more information, please see HTTP Header Configuration.
You can download CDN access logs in the CDN Console. For detailed directions, please see Log Download.
The self-diagnosis tool provides a range of diagnostic features such as testing for DNS resolution, linkage quality, site availability, and data access consistency for the accessed domain name. For more information, please see Self-Diagnosis Tool. The tool is subject to the configuration of the local network environment and cannot fully represent the entire network testing results.
Local access diagnosis: when you find an exception with one of your resource accesses, you can initiate a test with ""local access diagnosis"".
User access diagnosis: when your users report an exception with their resource accesses, you can pinpoint the problem through ""user access diagnosis"" and troubleshoot the problem according to Tencent Cloud's suggestions.
Yes. By default, CDN supports the origin server's
Yes. To help you save traffic, CDN compresses files between 256 bytes and 2,048 KB with filename extensions of .js, .html, .css, .xml, .json, .shtml, and .htm into gzip files.
Yes. CDN acceleration supports ports 80, 443, and 8080.
A CDN intermediate server is a middle-layer origin-pull server located between the business server and the CDN node. The intermediate server converges the node's origin-pull requests to reduce the origin-pull pressure on your origin server.
After a request goes through an edge server, a
x-forward-for header that includes the client's real IP information will be added to the request.
Sub-users do not need to register for Tencent Cloud or activate the CDN service. They are added to the sub-user list by the creator. There are two types of sub-users:
CDN supports IP blocklist/allowlist configuration. You can create filtering policies for source IPs of user requests based on your business needs, helping prevent hotlinking and attacks from malicious IPs. For more information, please see IP Blocklist/Allowlist Configuration.
Log in to the CDN Console, select Domain Management on the left sidebar, and click Manage on the right of the domain name you want to edit. For more information, please see Range GETs Configuration.
Click Origin Configuration and you will see the ""Range GETs Configuration"" module.
If your primary origin server is an external one, you can add a hot backup origin server. All origin-pull requests will be forwarded to the primary origin server first. If a 4XX or 5XX error code is returned or an exception such as connection timeout or protocol incompatibility occurs, requests will be forwarded to the hot backup origin server to pull resources, ensuring high availability of origin-pull.
No. Currently, CDN does not support domain names suffixed with .pw or .top.
Yes. The maximum size of a file that can be uploaded to CDN is 32 MB by default.
No. Currently, CDN does not support Chinese domain names (even after transcoding).
No. Currently, CDN can only forward requests to the origin server over the public network.
Yes. CDN currently uses Lua scripts to implement programmable configuration, which are generally used for customization and written and released by the CDN technical support team
Yes. CDN supports origin-pull to different origin servers for different client requests. You can submit a description of your specific requirements, and the CDN technical support team will configure for you on the backend.
If the primary origin server responds exceptionally, it can redirect requests to the configured backup origin server in sequence for request again.