HTTP Status Codes: A Developer's Quick Reference
Choosing the right HTTP status code communicates your API's intent clearly. Learn when to use each status code family and the most important codes in each range.
Hash Generator
Generate SHA-1, SHA-256, SHA-384, SHA-512 hashes from text
The Five Families
HTTP status codes are grouped into five families: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), and 5xx (server error). Each family communicates a different class of response.
2xx Success Codes
200 OK β the standard success response for GET and PUT requests. 201 Created β return this for successful POST requests that create a resource, with a Location header pointing to the new resource. 204 No Content β use for successful DELETE requests or updates that return no body. 202 Accepted β the request is queued for processing but not yet complete (asynchronous operations).
3xx Redirection Codes
301 Moved Permanently β the resource has a new URL permanently; search engines transfer ranking. 302 Found β temporary redirect; search engines keep indexing the original URL. 304 Not Modified β the resource hasn't changed since the client's last request (used with caching headers).
4xx Client Error Codes
400 Bad Request β the request body or parameters are malformed. Include a descriptive error message. 401 Unauthorized β authentication is required or the provided credentials are invalid. 403 Forbidden β the authenticated user doesn't have permission. 404 Not Found β the resource doesn't exist. 409 Conflict β the request conflicts with the current state (e.g., duplicate email). 422 Unprocessable Entity β the request is syntactically correct but semantically invalid (validation errors). 429 Too Many Requests β rate limit exceeded; include a Retry-After header.
5xx Server Error Codes
500 Internal Server Error β an unexpected error occurred; log the details server-side. 502 Bad Gateway β the server acting as proxy received an invalid response from upstream. 503 Service Unavailable β the server is temporarily overloaded or in maintenance; include Retry-After. 504 Gateway Timeout β the upstream server didn't respond in time.
κ΄λ ¨ λꡬ
κ΄λ ¨ ν¬λ§·
κ΄λ ¨ κ°μ΄λ
JSON vs YAML vs TOML: Choosing a Configuration Format
Configuration files are the backbone of modern applications. JSON, YAML, and TOML each offer different trade-offs between readability, complexity, and tooling support that affect your development workflow.
How to Format and Validate JSON Data
Malformed JSON causes silent failures in APIs and configuration files. Learn how to format, validate, and debug JSON documents to prevent integration errors and improve readability.
Base64 Encoding: How It Works and When to Use It
Base64 converts binary data into ASCII text, making it safe for transmission through text-based systems. Learn when Base64 is the right choice and when alternatives like hex encoding or URL encoding are more appropriate.
Best Practices for Working with Unix Timestamps
Unix timestamps provide a language-agnostic way to represent points in time, but they come with pitfalls around time zones, precision, and the 2038 problem. This guide covers best practices for storing and converting timestamps.
Troubleshooting JWT Token Issues
JSON Web Tokens are widely used for authentication but can be frustrating to debug. This guide covers common JWT problems including expiration errors, signature mismatches, and payload decoding issues.