Status Code Comparisons

41 side-by-side comparisons of commonly confused or related status codes.

# HTTP (14)

HTTP 301 Moved Permanently vs 302 Found
Compare HTTP 301 Moved Permanently vs 302 Found. Learn when to use permanent vs temporary redirects for SEO, caching, and method preservation.
HTTP 301 Moved Permanently vs 308 Permanent Redirect
Compare HTTP 301 vs 308 permanent redirects. Learn how 308 preserves HTTP methods while 301 may rewrite POST to GET.
HTTP 302 Found vs 307 Temporary Redirect
Compare HTTP 302 Found vs 307 Temporary Redirect. Learn how 307 preserves HTTP methods while 302 may rewrite POST to GET.
HTTP 307 Temporary Redirect vs 308 Permanent Redirect
Compare HTTP 307 vs 308 redirects. Both preserve HTTP methods, but 307 is temporary and 308 is permanent. Learn when to use each.
HTTP 301 Moved Permanently vs 307 Temporary Redirect
Compare HTTP 301 vs 307 redirects. 301 is permanent (may change method), 307 is temporary (preserves method). Learn the right choice.
HTTP 401 Unauthorized vs 403 Forbidden
Compare HTTP 401 Unauthorized vs 403 Forbidden. 401 means missing credentials, 403 means insufficient permissions. Learn the difference.
HTTP 400 Bad Request vs 422 Unprocessable Content
Compare HTTP 400 Bad Request vs 422 Unprocessable Content. 400 is for malformed syntax, 422 for semantic validation errors.
HTTP 404 Not Found vs 410 Gone
Compare HTTP 404 Not Found vs 410 Gone. 404 is ambiguous, 410 means permanently removed. Learn SEO and caching implications.
HTTP 500 Internal Server Error vs 502 Bad Gateway
Compare HTTP 500 Internal Server Error vs 502 Bad Gateway. 500 is an app crash, 502 is a proxy-to-upstream failure.
HTTP 500 Internal Server Error vs 503 Service Unavailable
Compare HTTP 500 vs 503. 500 is an unexpected server error, 503 is a temporary condition with Retry-After. Learn when to use each.
HTTP 502 Bad Gateway vs 504 Gateway Timeout
Compare HTTP 502 Bad Gateway vs 504 Gateway Timeout. 502 means invalid upstream response, 504 means upstream timed out.
HTTP 200 OK vs 201 Created
Compare HTTP 200 OK vs 201 Created. 200 is general success, 201 means a resource was created. Learn proper REST API usage.
HTTP 200 OK vs 204 No Content
Compare HTTP 200 OK vs 204 No Content. 200 includes a response body, 204 signals success with no content. Learn proper API design.
HTTP 429 Too Many Requests vs 503 Service Unavailable
Compare HTTP 429 Too Many Requests vs 503 Service Unavailable. 429 is client rate limiting, 503 is server-wide downtime.

# Cross-Protocol (13)

HTTP 404 Not Found vs gRPC 5 NOT_FOUND
Compare HTTP 404 Not Found vs gRPC NOT_FOUND. Same concept, different protocols. Learn how resource lookup errors differ across HTTP and gRPC.
HTTP 401 Unauthorized vs gRPC 16 UNAUTHENTICATED
Compare HTTP 401 Unauthorized vs gRPC UNAUTHENTICATED. Both mean missing credentials. Learn the naming confusion and gateway mapping.
HTTP 403 Forbidden vs gRPC 7 PERMISSION_DENIED
Compare HTTP 403 Forbidden vs gRPC PERMISSION_DENIED. Both mean authenticated but not authorized. Learn the cross-protocol mapping.
HTTP 500 Internal Server Error vs gRPC 13 INTERNAL
Compare HTTP 500 Internal Server Error vs gRPC INTERNAL. Both are catch-all server errors. Learn the cross-protocol equivalence.
HTTP 503 Service Unavailable vs gRPC 14 UNAVAILABLE
Compare HTTP 503 Service Unavailable vs gRPC UNAVAILABLE. Both signal temporary downtime. Learn retry strategies for each protocol.
HTTP 404 Not Found vs DNS NXDOMAIN (RCODE 3)
Compare HTTP 404 Not Found vs DNS NXDOMAIN. One is a missing URL path, the other is a missing domain. Learn the network layer difference.
HTTP 500 Internal Server Error vs WebSocket 1011 Internal Error
Compare HTTP 500 vs WebSocket 1011 Internal Error. Same meaning, different models: request-response vs persistent connection.
HTTP 401 Unauthorized vs SIP 401 Unauthorized
Compare HTTP 401 vs SIP 401 Unauthorized. Same code, different auth: Bearer tokens vs Digest nonces. Learn cross-protocol authentication.
HTTP 200 OK vs SIP 200 OK
Compare HTTP 200 OK vs SIP 200 OK. HTTP completes a request; SIP 200 starts a call session. Learn the protocol-specific semantics.
HTTP 200 OK vs gRPC 0 OK
Compare HTTP 200 OK vs gRPC 0 OK. gRPC OK is a trailer inside HTTP 200. Learn why HTTP status alone misses gRPC errors.
HTTP 408 Request Timeout vs gRPC 4 DEADLINE_EXCEEDED
Compare HTTP 408 Request Timeout vs gRPC DEADLINE_EXCEEDED. HTTP is server-side timeout, gRPC is client-set deadline. Learn the difference.
HTTP 409 Conflict vs gRPC 6 ALREADY_EXISTS
Compare HTTP 409 Conflict vs gRPC ALREADY_EXISTS. HTTP 409 covers all conflicts, gRPC is create-specific. Learn the mapping.
HTTP 429 Too Many Requests vs gRPC 8 RESOURCE_EXHAUSTED
Compare HTTP 429 Too Many Requests vs gRPC RESOURCE_EXHAUSTED. Both handle rate limiting, but gRPC is broader. Learn the mapping.

# SIP (6)

# SMTP (3)

# FTP (3)

# DNS (2)