📋 HTTP Status Code Reference

🔍
📖
{{ selectedCode.code }} {{ selectedCode.name }}

{{ selectedCode.description }}

Common Use Cases:

  • {{ useCase }}

Example:

{{ selectedCode.example }}
RFC Reference: {{ selectedCode.rfc }}
📋
Showing {{ filteredCodes.length }} of {{ statusCodes.length }} codes
No status codes match your search criteria.
{{ code.code }}
{{ code.name }}
{{ code.description }}
{{ getCategoryName(code.code) }}
📊
{{ getCategoryCount(category.code) }}
{{ category.name }}
⚡
{{ code.code }} {{ code.name }}
{{ code.frequency ||'Common' }}
⚠️ {{ error }}
📚

Complete HTTP Status Code Reference

Code
Name
Category
Description
RFC
{{ code.code }}
{{ code.name }}
{{ getCategoryName(code.code) }}
{{ code.description }}
{{ code.rfc }}
{{ getCategoryCount(category.code) }}
{{ category.name }}
codes
{{ statusCodes.length }}
Total
codes

ℹ️ About HTTP Status Code Reference

HTTP status codes are three-digit response codes sent by a server after it receives an HTTP request. The numeric code is the important part of the response line: it tells clients whether a request is still in progress, succeeded, needs a redirect, failed because of the request, or failed because of the server.

Status code classes:

  • 1xx informational: interim responses such as 100 Continue or 103 Early Hints.
  • 2xx success: the request was accepted, created, completed, or returned partial content.
  • 3xx redirection: the client should use another URI, a cached copy, or another representation.
  • 4xx client error: the request cannot be processed as sent, often because of syntax, authentication, permissions, validation, or rate limits.
  • 5xx server error: the server, proxy, or upstream service failed while handling an apparently valid request.

Practical uses:

  • Choose API responses such as 200 OK, 201 Created, 202 Accepted, and 204 No Content.
  • Debug browser, reverse proxy, load balancer, and CDN failures by comparing 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout.
  • Design redirects with the right permanence and method behavior: 301 or 308 for permanent moves, 302 or 307 for temporary redirects.
  • Document webhook and OpenAPI contracts with precise failure states such as 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 409 Conflict, and 422 Unprocessable Content.
  • Explain SEO and caching behavior around 301 Moved Permanently, 304 Not Modified, 410 Gone, and 451 Unavailable For Legal Reasons.

Implementation examples:

  • POST /users -> 201 Created plus a Location header when a new resource URL is available.
  • DELETE /sessions/current -> 204 No Content when the operation succeeds and no response body is needed.
  • PUT /documents/42 -> 409 Conflict or 412 Precondition Failed when optimistic locking or an If-Match precondition fails.
  • GET /api/report -> 429 Too Many Requests with Retry-After when a client has exceeded a rate limit.

Limitations: this page is a searchable reference, not a live URL checker. It does not send HTTP requests, inspect response headers, or verify how a browser follows redirects. Some codes are extension, WebDAV, historical, or rarely deployed codes, so use the status meaning and the current registry before adding one to a public API.

Primary sources: core HTTP status semantics are defined in RFC 9110 Section 15 and registered by the IANA HTTP Status Code Registry. Extension and specialized status codes are covered by sources such as RFC 4918 WebDAV, RFC 6585 additional status codes, RFC 8297 Early Hints, RFC 8470 Too Early, and RFC 7725 legal obstacles.

API Usage Example:

POST /api/tools/webdev/http-status-reference
Content-Type: application/json

{
    "category": "2xx",
    "search": "success",
    "includeExamples": true
}
Ready