HTTP status codes

更新时间:
复制 MD 格式

EdgeRoutine (ER) can return two error HTTP status codes or cause response interruptions.

HTTP status codes

ER may return the 598 or 599 HTTP status code based on the cause of the error.

Status code

Description

598

  • Execution fails due to rate limiting, which is caused by too many concurrent requests or an overloaded node.

  • Execution is blocked by an exception. Common causes include:

    • Two consecutive OOMs in the ER virtual machine within 5 seconds cause the ER to be disabled due to an exception.

    • ER execution is blocked for other internal reasons.

599

  • An uncaught exception occurs while processing the request context, preventing ER from continuing execution.

  • An uncaught exception occurs during the context initialization phase, preventing ER execution.

Exceptions

ER asynchronously generates responses in pass-through mode. If an exception occurs during this process, the client may receive only a partial response. Possible causes and solutions include:

  • A logic bug in your ER code triggers a JavaScript (JS) exception during response generation.

  • Resource limits are exceeded. In this case, you can submit a ticket for assistance.

Note

If you frequently receive truncated responses from ER, first check your code for bugs. If the code is correct, consider increasing your resource quota.