💬
Debugging & Tutorials
18 Essential HTTP Status Codes You Should Know in 2024
A
Anthony Olajide
Jan 2, 2026 at 2:56 PM
✅ 2xx Success
• 200 OK: Request succeeded
• 201 Created: New resource created
• 202 Accepted: Request in progress
• 204 No Content: Success, but no content to return
↪️ 3xx Redirection
• 301 Moved Permanently: Resource has new permanent URL
• 302 Found: Resource temporarily at different URL
• 304 Not Modified: Resource unchanged since last request
❌ 4xx Client Errors
• 400 Bad Request: Client-side error (e.g., invalid syntax)
• 401 Unauthorized: Authentication required
• 403 Forbidden: Server refuses to fulfill request
• 404 Not Found: Resource doesn't exist
• 405 Method Not Allowed: HTTP method not supported
• 408 Request Timeout: Server waited too long for request
🚫 5xx Server Errors
• 500 Internal Server Error: Unexpected server condition
• 501 Not Implemented: Server lacks required functionality
• 502 Bad Gateway: Invalid upstream server response
• 503 Service Unavailable: Server temporarily unavailable
• 504 Gateway Timeout: Upstream server timed out
Understanding these codes is crucial for robust error handling and seamless user experiences.
Gif Credit - [s][[/s]Nelson Djalo](https://www.linkedin.com/in/nelsonamigoscode/)
• 200 OK: Request succeeded
• 201 Created: New resource created
• 202 Accepted: Request in progress
• 204 No Content: Success, but no content to return
↪️ 3xx Redirection
• 301 Moved Permanently: Resource has new permanent URL
• 302 Found: Resource temporarily at different URL
• 304 Not Modified: Resource unchanged since last request
❌ 4xx Client Errors
• 400 Bad Request: Client-side error (e.g., invalid syntax)
• 401 Unauthorized: Authentication required
• 403 Forbidden: Server refuses to fulfill request
• 404 Not Found: Resource doesn't exist
• 405 Method Not Allowed: HTTP method not supported
• 408 Request Timeout: Server waited too long for request
🚫 5xx Server Errors
• 500 Internal Server Error: Unexpected server condition
• 501 Not Implemented: Server lacks required functionality
• 502 Bad Gateway: Invalid upstream server response
• 503 Service Unavailable: Server temporarily unavailable
• 504 Gateway Timeout: Upstream server timed out
Understanding these codes is crucial for robust error handling and seamless user experiences.
Gif Credit - [s][[/s]Nelson Djalo](https://www.linkedin.com/in/nelsonamigoscode/)
5 Replies
Sign in to join the conversation
d
diltony@yahoo.com
6 days ago
I love this, most times, the common ones we devs memorize are 301, 404, 500. But they are all important in building a standard, scalable restful API.
A
Anthony Olajide
6 days ago
@"dhtml"#p965 thanks for the comment. I think the server throws 500 by itself in some languages and 404 when it cannot find a resource.
d
diltony@yahoo.com
6 days ago
@"Simplythebest"#p966 while this is true, in some frameworks like laravel, you can do stuffs like:
abort(404), abort(500) to terminate a request with an error code.
abort(404), abort(500) to terminate a request with an error code.
A
Anthony Olajide
6 days ago
@"dhtml"#p967 thanks for that, I understand better now.
A
Anthony Olajide
6 days ago
@"dhtml"#p965
na only 404 and 500 i sabi , the most common one has to be 404
na only 404 and 500 i sabi , the most common one has to be 404