HTTP Status Codes
Complete reference for all HTTP status codes (1xx-5xx). Descriptions, common use cases, and troubleshooting tips.
📖 HTTP Status Codes: The Silent Language of the Web
Behind every click and every page load, a silent conversation is happening. Your browser asks, and the server answers—not with words, but with three-digit numbers. 'Success(200)', 'I moved(301)', 'You're not allowed(403)', 'I can't find it(404)'. I've spent countess nights debugging API calls, wondering why my data isn't showing up, only to find a single 4xx error was the key to the whole mystery.
KitPunch’s HTTP reference is your translator for this invisible dialogue. We've organized everything from 1xx (Informational) to 5xx (Server Error) to help you understand exactly what's happening 'under the hood.' Knowing these codes is the difference between a developer who is guessing and a developer who knows exactly where to look. Let's decode the signals together.
🚀 How to Use the Status Code Guide
- Enter the status code number in the search bar when you see one in your console.
- Identify the category (Client Error, Success, etc.) to know who the 'owner' of the problem is.
- Read the detailed explanation and common causes to identify the fix for your code.
- Use the filter buttons to browse all codes within a specific class (e.g., all 5xx errors).
💡 API Design Etiquette
When building an API, don't just return a generic 200 OK for everything. Be descriptive! Use 201 Created when a resource is made, and 422 Unprocessable Content for validation errors. Descriptive status codes make you a 'hero' to the frontend developers who have to use your API.
❓ Frequently Asked Questions
401 means 'I don't know who you are (Unauthorized)', so you need to log in. 403 means 'I know who you are, but you don't have permission to do this (Forbidden)'.
Use 301 for permanent moves—it tells Google to forget the old URL. Use 302 for temporary moves, like a maintenance page or a limited-time sale; it keeps the SEO value on the original page.