This topic describes HTTP status codes that EdgeRoutine (ER) may return and exceptions that may occur when you use ER.

HTTP status codes

ER may return the 598 or 599 HTTP status code based on the cause of the error. The following table describes the HTTP status codes.

Status code Description
598
  • ER is throttled and cannot process the request. Throttling occurs when the number of concurrent requests exceeds the limit or the node has insufficient processing capacity.
  • ER is not allowed to process requests due to certain exceptions. Possible causes include:
    • The virtual machine where ER is deployed encounters the out of memory (OOM) error several times. If the OOM error appears twice within five minutes, ER is not allowed to process requests.
    • Other causes.
599
  • An unknown error occurs when ER requests the context. As a result, ER is not allowed to process the request.
  • An unknown error occurs when ER initializes the context. As a result, ER is not allowed to process the request.

Exceptions

This error occurs because ER asynchronously generates a response when it responds to a request. As a result, ER is interrupted. ER transmits data in pass-through mode. When the preceding exception occurs, the client receives only part of the response. Possible causes and solutions include:

  • The code submitted to ER contains bugs that cause JavaScript exceptions when ER responds to requests.
  • If the exceptions are caused by resource limits, you can submit a ticket.
Note If ER is frequently interrupted when it responds to requests, check whether the code contains coding errors. If the code does not contain errors, we recommend that you contact your sales manager to increase your resource quota.