Reference for Abnormal Status Codes

Download

フォーカスモード

フォントサイズ

最終更新日: 2026-07-23 17:16:00

EdgeOne responds with the following types of exception status codes:
Standard Status Codes
You can refer to the HTTP Status Code Standard to see the specific meanings of these status codes. These codes are typically responded to in the following situations:
After the request is sent back to the origin, the status code information is responded by the origin server, and the node will pass transmit status code from the origin server to the client.
Direct responses from EdgeOne nodes, for example, Token authentication fails, responding with a 403 status code. Possible status codes that may be directly responded by EdgeOne nodes include the following status ones:
Status Code
Description
400
The client request is invalid, such as when the request Method is not within the allowed range of EdgeOne. For details, see HTTP Restrictions.
403
Failed hotlink protection validation, such as Rules Engine's Token authentication.
Compliance blocking triggered.
416
range abnormality, such as rangeStart < 0, rangeStart > rangeEnd, rangeStart > FileSize.
418
For domains connected to EdgeOne, the system automatically assigns service nodes to the domain. The corresponding nodes will distribute the domain's configuration file, with content determined by the domain's settings such as origin server, caching, headers, and so on. When a request is sent to a node, the node reads the domain's configuration file. If the configuration file is found to be missing, it responds with a 418 status code.
For example, if a client requests https://example.com/test.jpg, the node will read the configuration file for the domain example.com. The client may receive a 418 response due to reasons such as the request being routed to a service node bound to a domain other than example.com, a CNAME configuration error, or a scheduling system exception.
423
A request loop is triggered, meaning the Loops value in the CDN-Loop header is greater than or equal to 16. For details, see CDN-Loop.
EdgeOne Custom Status Codes
EdgeOne defines special status codes with unique meanings. Status codes within the range of 520-599 are reserved by EdgeOne for custom non-standard responses. It is recommended to avoid using status codes within this range in your business to prevent confusion with EdgeOne's status codes.
﻿
The following are EdgeOne's custom exception status codes and their meaning descriptions, which facilitate your self-service troubleshooting when business access is abnormal. For more troubleshooting details, see the EdgeOne 4XX/5XX Status Code Troubleshooting Guide.
Status Code
Description
520/550
After a successful connection is established between the node and the origin server, the node sends a request to the origin server. If the origin server directly sends an RST packet, the node responds to the client with a 520/550 status code.
521/551
After the node requests the origin server, during the TCP connection establishment phase, if the origin server directly sends an RST packet, the node responds to the client with a 521/551 status code.
522/552
When the node requests the origin server during the TCP connection establishment phase, and the origin server fails to respond, causing the node to time out, the node responds to the client with a 522/552 status code.
523/553
If the origin server configured for the domain is a domain name itself, when the node attempts to back to the origin, it needs to resolve this domain name to obtain the origin server's IP address. If the resolution fails, the node cannot proceed to the origin and responds to the client with a 523/553 status code.
524/554
If the origin server fails to respond after a successful connection is established between the node and the origin server and the node sends a request, causing the node to time out, the node responds to the client with a 524/554 status code.
525/555
If the origin-fetch protocol is HTTPS, the node needs to perform an SSL handshake with the origin server when fetching content. If the handshake fails, the node responds to the client with 525/555 status code.
545
Edge Function execution exception, such as referencing an undefined variable.
566
When a request is intercepted by Web Protection - Managed Rules , it responds with the default 566 status code and the default block page by default. If the user configures a custom block status code, the user-configured status code will be used.
567
When a request is intercepted by Web Protection - Custom Rules, Web Protection - Rate Limit , or Bot Management  rules, it responds with the default 567 status code and the default block page by default. If the user configures a custom block status code, the user-configured status code will be used.
570
Platform-level rate limiting is triggered. It is a static rate limiting policy set by EdgeOne to ensure overall platform stability. Regardless of whether a node is currently under high load, this policy is triggered as long as requests meet the platform's preset fixed rate limiting conditions.
571
Domain-level rate limiting is triggered. It is a static rate limiting policy set by EdgeOne by default for domains. Regardless of whether a node is currently under high load, this policy is triggered as long as requests meet the configured fixed rate limiting conditions.
579
Dynamic rate limiting is triggered. It is a dynamic rate limiting policy of EdgeOne, which differs from the fixed-threshold judgment of 570/571 and is triggered only when a node is under high load and a request surge occurs. The system limits the rate for requests with abnormally high growth by counting the request volume over a recent period and calculating its growth amount/rate.
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿

ヘルプとサポート

この記事はお役に立ちましたか？

営業担当者にお問い合わせいただくかチケットを提出してサポートを求めることができます。

フィードバック

tencent cloud

Tencent Cloud EdgeOne

Reference for Abnormal Status Codes

Standard Status Codes

EdgeOne Custom Status Codes

ヘルプとサポート

Status Code	Description
400	The client request is invalid, such as when the request Method is not within the allowed range of EdgeOne. For details, see HTTP Restrictions.
403	Failed hotlink protection validation, such as Rules Engine's Token authentication. Compliance blocking triggered.
416	range abnormality, such as rangeStart < 0, rangeStart > rangeEnd, rangeStart > FileSize.
418	For domains connected to EdgeOne, the system automatically assigns service nodes to the domain. The corresponding nodes will distribute the domain's configuration file, with content determined by the domain's settings such as origin server, caching, headers, and so on. When a request is sent to a node, the node reads the domain's configuration file. If the configuration file is found to be missing, it responds with a 418 status code. For example, if a client requests `https://example.com/test.jpg`, the node will read the configuration file for the domain `example.com`. The client may receive a 418 response due to reasons such as the request being routed to a service node bound to a domain other than `example.com`, a CNAME configuration error, or a scheduling system exception.
423	A request loop is triggered, meaning the Loops value in the CDN-Loop header is greater than or equal to 16. For details, see CDN-Loop.

Status Code	Description
520/550	After a successful connection is established between the node and the origin server, the node sends a request to the origin server. If the origin server directly sends an RST packet, the node responds to the client with a 520/550 status code.
521/551	After the node requests the origin server, during the TCP connection establishment phase, if the origin server directly sends an RST packet, the node responds to the client with a 521/551 status code.
522/552	When the node requests the origin server during the TCP connection establishment phase, and the origin server fails to respond, causing the node to time out, the node responds to the client with a 522/552 status code.
523/553	If the origin server configured for the domain is a domain name itself, when the node attempts to back to the origin, it needs to resolve this domain name to obtain the origin server's IP address. If the resolution fails, the node cannot proceed to the origin and responds to the client with a 523/553 status code.
524/554	If the origin server fails to respond after a successful connection is established between the node and the origin server and the node sends a request, causing the node to time out, the node responds to the client with a 524/554 status code.
525/555	If the origin-fetch protocol is HTTPS, the node needs to perform an SSL handshake with the origin server when fetching content. If the handshake fails, the node responds to the client with 525/555 status code.
545	Edge Function execution exception, such as referencing an undefined variable.
566	When a request is intercepted by Web Protection - Managed Rules , it responds with the default 566 status code and the default block page by default. If the user configures a custom block status code, the user-configured status code will be used.
567	When a request is intercepted by Web Protection - Custom Rules, Web Protection - Rate Limit , or Bot Management rules, it responds with the default 567 status code and the default block page by default. If the user configures a custom block status code, the user-configured status code will be used.
570	Platform-level rate limiting is triggered. It is a static rate limiting policy set by EdgeOne to ensure overall platform stability. Regardless of whether a node is currently under high load, this policy is triggered as long as requests meet the platform's preset fixed rate limiting conditions.
571	Domain-level rate limiting is triggered. It is a static rate limiting policy set by EdgeOne by default for domains. Regardless of whether a node is currently under high load, this policy is triggered as long as requests meet the configured fixed rate limiting conditions.
579	Dynamic rate limiting is triggered. It is a dynamic rate limiting policy of EdgeOne, which differs from the fixed-threshold judgment of 570/571 and is triggered only when a node is under high load and a request surge occurs. The system limits the rate for requests with abnormally high growth by counting the request volume over a recent period and calculating its growth amount/rate.