//
Comprehensive reference directory of standard HTTP response status codes with official RFC definitions, caching rules, and debugging solutions.
Standard response for successful HTTP requests. The payload content depends on the request method.
Use for successful GET, PUT, or PATCH requests returning requested data representation.
HTTP/1.1 200 OK
Content-Type: application/json
{
"status": "success",
"data": { "id": "usr_100", "name": "Alex" }
}HTTP status codes are categorized by their first digit into five distinct functional classes:
100 Continue, 101 Switching Protocols for WebSockets).200 OK, 201 Created for REST POST, 204 No Content for DELETE).301 Moved Permanently for SEO link equity transfer, 302 Found for temporary redirects, 304 Not Modified for conditional browser caching).400 Bad Request, 401 Unauthorized / missing credentials, 403 Forbidden, 404 Not Found, 429 Too Many Requests / rate limiting).500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout).Correct HTTP status code selection is vital for search engine crawling and REST API client stability. For instance, using a 301 Moved Permanently redirect preserves link equity and passes search ranking power, whereas a temporary 302 tells search engines to retain the old URL in the index.
404, 502) or keyword (e.g. redirect, unauthorized) into the instant search bar.Scenario: Migrating a legacy URL path to a new canonical route while preserving Google rankings.
Status: 301 Moved Permanently
HTTP/1.1 301 Moved Permanently Location: https://example.com/new-path Cache-Control: public, max-age=31536000
Tells search engines to transfer 100% of link equity to the new canonical URL.
Scenario: Responding to a successful POST request creating a new database record.
Status: 201 Created
HTTP/1.1 201 Created
Location: /api/users/102
Content-Type: application/json
{"id": 102, "name": "Alex"}Confirms resource creation and provides destination location header.