- The 2xx Family (Success) These are the ones we like.
200 OK: The standard response for a successful HTTP request. The server did its job.
201 Created: Usually returned after a successful POST request (like creating a new user or posting a new article). The resource was successfully created.
If you are seeing these, your API is working perfectly. Go grab a coffee. ☕
- The 3xx Family (Redirection) This is where SEO and infrastructure issues usually begin.
301 Moved Permanently: The resource has been permanently moved to a new URL. Pro Tip: Always use 301s when migrating websites to preserve your Google SEO ranking.
302 Found (Temporary Redirect): The resource is temporarily at a different URL. Don't use this for permanent moves, or search engines will get confused.
- The 4xx Family (Client-Side Errors) This means the client (the browser or the developer) messed up.
400 Bad Request: The server cannot process the request due to a client error (e.g., malformed request syntax, invalid JSON).
401 Unauthorized: You are not authenticated. You haven't logged in, or your API token is missing/invalid.
403 Forbidden: You are authenticated, but you don't have permission to access this resource. (e.g., a normal user trying to access an admin panel).
404 Not Found: The classic. The server can't find the requested resource. It's either deleted or the URL is wrong.
- The 5xx Family (Server-Side Errors) The server failed to fulfill a valid request. This is where backend developers start sweating.
500 Internal Server Error: The catch-all error. It means the server encountered an unexpected condition. You need to check your backend logs immediately.
502 Bad Gateway: Your reverse proxy (Nginx/Apache) tried to talk to your backend service (PHP-FPM, Node.js), but the backend gave an invalid response. Usually caused by the backend crashing or timing out.
504 Gateway Timeout: Similar to 502, but the backend simply took too long to respond. Your server might be overwhelmed or the script is running an infinite loop.
🛠️ How to Debug Status Codes Quickly (Without Terminal)
When you are building an API or migrating a server, your browser's developer tools are great. But what if you just want to check if a specific URL is returning the right status code right now without opening Postman or writing a cURL command?
I used to open my terminal, type curl -I https://example.com, and read the headers. It works, but it breaks my flow.
To speed this up, I recently started using a lightweight web toolset called Site Tools Box.
They have a free HTTP Status Checker that does exactly one thing, and does it well:
You paste the URL.
It instantly returns the Status Code, Response Headers, and Response Time.
(No, you don't need to sign up, and it doesn't throw 50 ads in your face.)
It’s incredibly useful when I need to quickly verify:
If my 301 redirects are properly configured.
If a website is actually down (is it a 502 or a 504?).
If an API endpoint requires auth (it will return a 401 immediately).
Wrap Up
Never underestimate the power of a status code. It is the fastest way to tell if the problem is in your frontend code, your network configuration, or your backend server.
Next time you get a 502, don't just restart the server blindly. Check the status code, read the headers, and use the right tools to isolate the issue.
Happy debugging! 🚀
Top comments (0)