HTTP Status Codes

Search and reference HTTP status codes with comprehensive descriptions and usage guides.

100
Continue
The server received the initial part of the request; the client should continue sending the rest
Informational
101
Switching Protocols
The server understands and agrees to the client's protocol switch request
Informational
102
Processing
The server received the request and is still processing it
Informational
200
OK
The request succeeded
Success
201
Created
The request succeeded and a new resource was created
Success
202
Accepted
The request was accepted but has not finished processing
Success
204
No Content
The request succeeded but there is no content to return
Success
206
Partial Content
The server successfully processed a partial GET request
Success
300
Multiple Choices
The request has more than one possible response
Redirection
301
Moved Permanently
The requested resource has moved permanently to a new location
Redirection
302
Found
The requested resource is temporarily served from a different URI
Redirection
304
Not Modified
Not modified; use the cached version
Redirection
307
Temporary Redirect
Temporary redirect, keeping the request method
Redirection
308
Permanent Redirect
Permanent redirect, keeping the request method
Redirection
400
Bad Request
The server cannot understand the request format
Client error
401
Unauthorized
The request requires authentication
Client error
403
Forbidden
The server refuses the request
Client error
404
Not Found
The requested resource does not exist
Client error
405
Method Not Allowed
The request method is not allowed
Client error
408
Request Timeout
The server timed out waiting for the request
Client error
409
Conflict
The request conflicts with the server's current state
Client error
410
Gone
The requested resource has been permanently deleted
Client error
413
Payload Too Large
The request entity is too large
Client error
414
URI Too Long
The request URI is too long
Client error
415
Unsupported Media Type
Unsupported media type
Client error
422
Unprocessable Entity
The request is well-formed but semantically incorrect
Client error
429
Too Many Requests
Too many requests
Client error
500
Internal Server Error
Internal server error
Server error
501
Not Implemented
The server does not support the requested functionality
Server error
502
Bad Gateway
Bad gateway
Server error
503
Service Unavailable
Service temporarily unavailable
Server error
504
Gateway Timeout
Gateway timeout
Server error

About HTTP Status Codes — Detailed Guide

Category: Network & HTTP 100% Browser-Local

The HTTP Status Code Reference provides an exhaustive dictionary of standard IETF RFC HTTP response status codes categorized across 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Errors), and 5xx (Server Errors).

Each entry features its canonical RFC name, in-depth architectural explanations, common trigger conditions, and troubleshooting remediation advice. Powered entirely by a client-side database, search results render instantly offline without network latency.

#http #status #code #404 #500 #200

Key Features & Capabilities

  • Comprehensive catalog of standard 1xx through 5xx HTTP/1.1 and HTTP/2 response codes
  • Deep architectural documentation outlining RFC origins, root causes, and debugging steps
  • Instant fuzzy search filtering by numeric code (e.g. 404, 503) or natural keywords
  • 100% offline static reference guide accessible without server dependencies

How to Use

  1. 1

    Enter a status code number (e.g., 504) or keyword (e.g., gateway, unauthorized) into the search bar.

  2. 2

    Click on any matching status card to expand its architectural breakdown.

  3. 3

    Review recommended diagnostics and error resolution practices for your application.

Common Use Cases

  • → Troubleshooting Nginx, Cloudflare, or reverse proxy 502 Bad Gateway and 504 Timeout errors
  • → Distinguishing between 401 Unauthorized and 403 Forbidden when designing API authentication
  • → Selecting semantically precise response codes for REST APIs (e.g. 201 Created vs. 204 No Content)

Related Tools

Frequently Asked Questions & Privacy

What is the operational difference between 301 and 302 redirects?

A 301 Moved Permanently tells browsers and search crawlers to cache the new target address permanently, while a 302 Found signifies a temporary redirect retaining the original URL in search indices.

When should an API return 422 Unprocessable Entity instead of 400 Bad Request?

HTTP 400 denotes malformed syntax (e.g., invalid JSON), whereas 422 denotes syntactically valid requests that violate semantic business rules (e.g., age cannot be negative).