HTTP documented errors

Browse documented HTTP errors with exact messages, troubleshooting context, and practical remediation steps.

Authentication Configuration General Networking Runtime

Back to all products

Authentication

Authentication errors

401 UnauthorizedHTTP 401 UnauthorizedThe request lacks valid authentication credentials for the target resource, so the server refused to authorize access.

403 ForbiddenHTTP 403 ForbiddenThe server understood the request but refuses to authorize it, even if the client retries with the same identity.

Configuration

Configuration errors

405 Method Not AllowedHTTP 405 Method Not AllowedThe server knows the target resource but does not allow the HTTP method used in the request.

409 ConflictHTTP 409 ConflictThe request conflicts with the current state of the target resource, so the server rejected the update or operation.

General

General errors

400 Bad RequestHTTP 400 Bad RequestThe server rejected the request because it considers the request malformed or invalid and will not process it as sent.

404 Not FoundHTTP 404 Not FoundThe server cannot find the requested resource at the given URL, though it does not necessarily indicate whether the absence is temporary or permanent.

410 GoneHTTP 410 GoneThe server indicates that the requested resource has been permanently removed and is not expected to return.

Networking

Networking errors

408 Request TimeoutHTTP 408 Request TimeoutThe server timed out waiting for the client to send a complete request in the allowed time window.

413 Content Too LargeHTTP 413 Content Too LargeThe server refused to process the request because the request body is larger than the server is willing or able to handle.

414 URI Too LongHTTP 414 URI Too LongThe server refused the request because the target URI is longer than the server is willing to interpret.

429 Too Many RequestsHTTP 429 Too Many RequestsThe client sent too many requests in a given time window and the server rate-limited further access temporarily.

502 Bad GatewayHTTP 502 Bad GatewayA server acting as a gateway or proxy received an invalid response from the upstream server it depends on.

504 Gateway TimeoutHTTP 504 Gateway TimeoutA gateway or proxy server did not receive a timely response from the upstream server it needed to complete the request.

Runtime

Runtime errors

500 Internal Server ErrorHTTP 500 Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.

503 Service UnavailableHTTP 503 Service UnavailableThe server is temporarily unable to handle the request, often because it is overloaded or down for maintenance.

HTTP Errors | Error Atlas