XTools
Loading...
🌐
HTTP Status Codes
Complete HTTP status codes reference with search and filteringSearch Status Codes
Status Codes
| Code | Name | HTTP Status Codes Reference | Category |
|---|---|---|---|
| 100 | Continue | Continue | Informational (1xx) |
| 101 | Switching Protocols | Switching Protocols | Informational (1xx) |
| 102 | Processing | Processing | Informational (1xx) |
| 103 | Early Hints | Early Hints | Informational (1xx) |
| 200 | OK | OK | Success (2xx) |
| 201 | Created | Created | Success (2xx) |
| 202 | Accepted | Accepted | Success (2xx) |
| 203 | Non-Authoritative Information | Non-Authoritative Information | Success (2xx) |
| 204 | No Content | No Content | Success (2xx) |
| 205 | Reset Content | Reset Content | Success (2xx) |
| 206 | Partial Content | Partial Content | Success (2xx) |
| 207 | Multi-Status | Multi-Status | Success (2xx) |
| 208 | Already Reported | Already Reported | Success (2xx) |
| 226 | IM Used | IM Used | Success (2xx) |
| 300 | Multiple Choices | Multiple Choices | Redirection (3xx) |
| 301 | Moved Permanently | Moved Permanently | Redirection (3xx) |
| 302 | Found | Found | Redirection (3xx) |
| 303 | See Other | See Other | Redirection (3xx) |
| 304 | Not Modified | Not Modified | Redirection (3xx) |
| 305 | Use Proxy | Use Proxy | Redirection (3xx) |
Categories
Informational (1xx)
Request received, processing continues
Success (2xx)
Request successfully received and processed
Redirection (3xx)
Further action required to complete request
Client Error (4xx)
Request contains bad syntax or cannot be fulfilled
Server Error (5xx)
Server failed to fulfill valid request
Common Status Codes
200 OK: The request has succeeded
301 Moved Permanently: The requested resource has been moved permanently
404 Not Found: The requested resource was not found
500 Internal Server Error: An internal server error occurred
HTTP status codes are essential for web development and API design. Understanding these codes helps in debugging, error handling, and creating better user experiences. Always handle different status codes appropriately in your applications.
📖 Usage Guide
Step 1: Browse Status Codes
Browse the comprehensive list of HTTP status codes organized by category (1xx, 2xx, 3xx, 4xx, 5xx).
Step 2: Search and Filter
Use the search function to find specific status codes by number, name, or description.
Step 3: Apply in Development
Use the status code information for proper HTTP response handling in web development and API design.
✨ Features
📊
Complete ListComprehensive list of all HTTP status codes
🔍
Search & FilterSearch and filter status codes by category or number
🏷️
Category TagsOrganized by HTTP status code categories
📖
Detailed InformationDetailed descriptions and usage examples for each status code
⚡
Quick ReferenceQuick lookup for common HTTP status codes
🌐
Web StandardsCompliant with RFC 7231 and HTTP/1.1 standards
🔬Technical Introduction
How HTTP Status Codes WorkHTTP status codes are three-digit numbers that indicate the outcome of an HTTP request. They provide information about whether the request was successful, encountered an error, or requires further action. Status codes are grouped into five classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
Best PracticesUse appropriate status codes for different scenarios: 200 for successful GET requests, 201 for successful POST requests, 400 for bad requests, 404 for not found, 500 for server errors. Always include meaningful error messages and handle status codes properly in client applications.
Common Status Code IssuesCommon issues include using 200 for all successful responses (use 201 for created resources), returning 404 for authentication failures (use 401 or 403), and not handling 3xx redirects properly. Always check the response body for additional error details.