| 400 |
HTTP 400 Bad Request |
The server could not understand the request because its syntax, headers or body are malformed or invalid. |
| 410 |
HTTP 410 Gone |
The resource used to exist but was intentionally and permanently removed, with no forwarding address. |
| 401 |
HTTP 401 Unauthorized |
The request has no valid authentication credentials — you need to log in or send a valid token. |
| 403 |
HTTP 403 Forbidden |
The server understood the request but refuses to authorize it — you (or the server process) are not allowed t… |
| 404 |
HTTP 404 Not Found |
The server can’t find anything at the requested URL. |
| 405 |
HTTP 405 Method Not Allowed |
The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route). |
| 407 |
HTTP 407 Proxy Authentication Required |
A proxy between you and the server requires credentials before it will forward your request. |
| 408 |
HTTP 408 Request Timeout |
The server closed the connection because the client took too long to send the complete request. |
| 409 |
HTTP 409 Conflict |
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdat… |
| 413 |
HTTP 413 Content Too Large (Request Entity Too Large) |
The request body is bigger than the server is willing to accept — usually a file upload over the configured l… |
| 415 |
HTTP 415 Unsupported Media Type |
The server refuses the request because the body’s Content-Type isn’t one it accepts. |
| 422 |
HTTP 422 Unprocessable Content |
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field). |
| 429 |
HTTP 429 Too Many Requests |
You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later. |
| 499 |
HTTP 499 Client Closed Request (Nginx) |
Nginx-specific code logged when the client disconnected before the server finished responding. |
| 500 |
HTTP 500 Internal Server Error |
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the applicatio… |
| 502 |
HTTP 502 Bad Gateway |
A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream s… |
| 503 |
HTTP 503 Service Unavailable |
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backen… |
| 504 |
HTTP 504 Gateway Timeout |
A proxy or gateway waited too long for the upstream server to respond and gave up. |