Release Notes
Security Announcement
Announcements
Status Code | Description |
400 | The client's request is deemed invalid because the requested method is not within the allowed range set by EdgeOne. For details, see HTTP Restrictions. |
403 | Fail to pass the link protection verification, such as the Token authentication in the rule engine. Trigger compliance blocking. |
416 | Range exception, for example, rangeStart < 0,< 0, rangeStart > rangeStart > rangeEnd, or rangeStart > FileSize. |
418 | For each domain name connected to EdgeOne, the system automatically allocates service nodes for the domain. Each corresponding node receives the domain's configuration file, which includes settings such as the origin server, cache, headers, etc. When a request is sent to a node, it reads the domain's configuration file. If the file is not found, the node responds with a 418 status code. For example, when a client requests: https://example.com/test.jpg, the node will read the configuration file for the domain example.com. Due to reasons such as the domain being bound to a service node that does not correspond to example.com, incorrect CNAME configuration, or anomalies in the scheduling system, the client may receive a 418 response. |
423 | Request loopback is triggered, that is, the Loops value in the CDN-Loop header is greater than or equal to 16. For details, see CDN-Loop. |
Status Code | Meaning Explanation |
520/550 | After the node successfully establishes a connection with the origin server and sends a request, if the origin server directly sends a RST packet, the node responds to the client with a 520/550 status code. |
521/551 | When the node requests the origin server, during the TCP connection establishment phase, if the origin server directly sends a 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, if the origin server does not respond, causing the node to time out, the node responds to the client with a 522/552 status code. |
523/553 | If the domain is configured with a domain name as the origin server, when the node goes to the origin, it needs to resolve the domain to obtain the origin server's IP. If the resolution fails, the node cannot go to the origin, and it responds to the client with a 523/553 status code. |
524/554 | After successfully establishing a connection with the origin server, if the node initiates a request to the origin server and there is no response from the origin server, causing a timeout at the node, the node responds to the client with a 524/554 status code. |
525/555 | If the origin protocol is HTTPS, the node needs to perform an SSL handshake with the origin server when going back to the source. If the handshake fails, the node responds to the client with a 525/555 status code. |
566 | When a request is intercepted by Web Protection - Managed Rules, the default response is a 566 status code along with the default interception page. If the user has configured a custom interception status code, the configured status code will be used. |
567 | When a request is intercepted by Web Protection - Custom Rules, Web Protection - Rate Limiting or Bot Management rules, the default response is a 567 status code along with the default interception page. If the user has configured a custom interception status code, the configured status code will be used. |
570 | Trigger platform-wide rate limiting. |
545 | Edge function execution exception, such as referencing undefined variables. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback