20 Essential HTTP Status Codes for Developers
A developer's day often involves navigating the intricate communication between client and server. When a request doesn't go as planned, understanding the server's response is key. For instance, a 404 Not Found code clearly indicates that the requested resource is absent, while a 500 Internal Server Error signals an unexpected issue on the server's end. Similarly, a 201 Created response confirms that a new resource has been successfully generated.
Each of these terms and their meanings can be added to Memorabit, which sends them as a reminder at an unexpected moment. The full list follows.
| Term | Meaning |
|---|---|
| 200 OK | The request has succeeded. |
| 201 Created | The request has been fulfilled and resulted in new resources being created. |
| 204 No Content | The server has fulfilled the request and there is no additional content to send. |
| 301 Moved Permanently | The resource has a new permanent URI; future references should use the new URI. The method may change from POST to GET. |
| 302 Found | The target resource resides temporarily under a different URI. |
| 304 Not Modified | A conditional GET or HEAD request was received and the condition evaluated to false. |
| 307 Temporary Redirect | The target resource resides temporarily under a different URI; the method must not change. |
| 308 Permanent Redirect | The resource has a new permanent URI; future references should use the new URI. The method is preserved. |
| 400 Bad Request | The server cannot process the request due to a client error. |
| 401 Unauthorized | The request has not been applied because it lacks valid authentication credentials. |
| 403 Forbidden | The server understood the request but refuses to fulfill it. |
| 404 Not Found | The origin server did not find a current representation for the target resource. |
| 405 Method Not Allowed | The method in the request-line is known by the server but not supported by the target resource. |
| 409 Conflict | The request could not be completed due to a conflict with the current state of the target resource. |
| 410 Gone | Access to the target resource is no longer available at the origin server and this is likely permanent. |
| 413 Content Too Large | The server is refusing to process a request because the content is larger than it can process. |
| 422 Unprocessable Content | The server understands the content type and syntax, but cannot process the instructions. |
| 500 Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 502 Bad Gateway | The server, acting as a gateway or proxy, received an invalid response from an inbound server. |
| 503 Service Unavailable | The server is currently unable to handle the request due to temporary overload or maintenance. |