tencent cloud

Content Delivery Network

Updates and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Product Overview
Strengths
Use Cases
Term
Use Limits
CDN Performance Descriptions (Spot-check)
Purchase Guide
CDN Purchase Guide
ECDN Purchase Guide
Getting Started
Configuring CDN from Scratch
Adding Domain Names
CNAME Configuration
Domain Name Ownership Verification
FAQs about Domain Name Connection
Configuration Guide
Domain Management
Domain Name Configurations
Statistical Analysis
Purge and Prefetch
Log Management
EdgeOne
Service Query
Offline Cache
Permission Management
Permission Configuration
Console Permissions
Activate Real-time Logging as Sub-account/Collaborator
Use Cases
Accelerating Resources on COS with CDN
Practical Tutorial
Guide to Using the EdgeOne Tool for Migrating Content Delivery Network (CDN) Related Services
CDN - CVM
CDN - COS
Configuring CNAME via DNSPod
Regularly Storing CDN Logs
API Documentation
History
Introduction
API Category
Content Management APIs
Real-time Log APIs
Service Query APIs
Data Query APIs
Making API Requests
Log Query APIs
StopCdnDomain
Configuration Management APIs
Obsoleted APIs
Other APIs
Data Types
Error Codes
FAQ
Features
Billing
FAQs about Domain Name Connection
Cache Configuration FAQs
Purge and Prefetch
Statistical Analysis
FAQs about HTTPS
Connection
Errors
Troubleshooting Methods
Status Codes and Solutions
Node Cache Inconsistency
Slow Access Speed After CDN Activation
Low Traffic Hit Rate
404 Status Code
Page Display - CORS error
Resource Cache Failure
Service Level Agreement
Glossary

Errors

PDF
Focus Mode
Font Size
Last updated: 2024-12-30 22:03:17

What should I do if a 423 error is reported in CDN?

The 423 status code is a Tencent Cloud CDN custom status code. CDN will report a 423 error when it detects a loopback request. We recommend you check the following:
1. Check the origin server configured in the CDN Console. If your origin server is also a Tencent Cloud CDN acceleration domain name, it may cause loopback requests.
2. If your origin server is configured with 301/302 HTTP to HTTP redirection and follow 301/302 is enabled in the CDN Console, a 423 error may occur. We recommend you disable follow 301/302.
Note:
if you use this method, we recommend you enable HTTPS configuration to force HTTPS redirection and change the origin-pull method to protocol follow. Otherwise, multiple redirects may occur. For the configuration steps, please see HTTPS Acceleration Configuration Guide.

What should I do if a 514 status code is returned in CDN?

This is caused by the IP access limit configured in the CDN Console as shown below:


Note:
IP access limit is designed to restrict the number of times an IP is allowed to access a node within one second. If the limit is exceeded, a 514 error will be returned.
Setting a low limit may affect the use of your business by normal high-frequency users. Therefore, please set a reasonable threshold. For more information, please see IP Access Limit Configuration.

What should I do if a 404 status code is returned by a CDN domain name?

Check the following:
1. Check whether the origin server can be accessed normally.
2. Check whether the origin server information and the origin domain have been modified in the CDN Console. This may have caused the 404 error during origin-pull.

Does CDN support switching to non-origin-pull automatically and return the content cached on a node in case of origin server exception?

In case of origin server exception, if the cache on the CDN node accessed by the user request has not expired, the node will directly return the requested content to the client. If the cache has expired, it will not respond and an origin-pull request will be initiated.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback