| Previous | Next |
| HTTP_STATUS_CLIENT_CLOSED_REQUEST | HTTP_STATUS_NOT_SUPPORTED |
HTTP_STATUS_SERVER_ERROR
The status intentionally does not identify the root cause. It can arise from unhandled application exceptions, configuration errors, failed dependencies, or a response that the server could not complete.
Correlate the request with server, proxy, and dependency logs using a request ID and timestamp. For clients, retry only when the operation is safe and the service documents retry behavior.
Operational meaning of HTTP 500 for HTTP_STATUS_SERVER_ERROR
HTTP 500 (this result) is a server-error response. AllStat records its meaning as “500 Internal Server Error”. Interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling
- Correlate this result with origin, gateway, load-balancer, and dependency logs to locate which hop generated it.
- record request and trace identifiers, upstream timing, retry count, and the health of the selected backend.
- use bounded retries with backoff only for idempotent work and only when the service policy permits them.
For telemetry, record HTTP 500, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.