## đź“ť Author
Birat Aryal — birataryal.github.io
Created Date: 2025-06-18
Updated Date: Wednesday 18th June 2025 10:53:15
Website - birataryal.com.np
Repository - Birat Aryal
LinkedIn - Birat Aryal
DevSecOps Engineer | System Engineer | Cyber Security Analyst | Network Engineer
HTTP Response Status Codes with Descriptions and Resolutions
1xx: Informational
| Code | Meaning | Use Case | Resolution |
|---|---|---|---|
| 100 | Continue | Client should continue with request body | |
| 101 | Switching Protocols | Used for upgrading to WebSocket or HTTP/2 | |
| 102 | Processing (WebDAV) | Server is processing request | |
| 103 | Early Hints | Preload resources before final response |
2xx: Success
| Code | Meaning | Use Case | Resolution |
|---|---|---|---|
| 200 | OK | Standard response for successful requests | |
| 201 | Created | Resource successfully created | |
| 202 | Accepted | Request accepted but processing not completed | |
| 203 | Non-Authoritative Info | Response from a proxy with modified content | |
| 204 | No Content | Success with no response body | |
| 205 | Reset Content | Client should reset view | |
| 206 | Partial Content | Partial data (range requests) |
3xx: Redirection
| Code | Meaning | Use Case | Resolution |
|---|---|---|---|
| 300 | Multiple Choices | Multiple resource options | Specify one preferred option or URL |
| 301 | Moved Permanently | Resource permanently moved | Update bookmarks or links to new URL |
| 302 | Found | Temporary redirect | Handle redirection on the client side |
| 303 | See Other | Redirect for safe GET retrieval | Follow redirect using GET method |
| 304 | Not Modified | Content hasn't changed | Ensure client caching is enabled properly |
| 305 | Use Proxy (deprecated) | Use a proxy for accessing resource | Not recommended; use standard proxy config |
| 307 | Temporary Redirect | Redirect while preserving method | Follow redirect URL with same method |
| 308 | Permanent Redirect | Like 301, but method is preserved | Update endpoint to the new URL |
4xx: Client Errors
| Code | Meaning | Use Case | Resolution |
|---|---|---|---|
| 400 | Bad Request | Invalid syntax or malformed request | Validate and fix request parameters or payload |
| 401 | Unauthorized | Authentication required or failed | Include correct authentication headers or tokens |
| 402 | Payment Required | Reserved; used by custom systems | Contact billing support if used in context |
| 403 | Forbidden | Authenticated but no permission | Ensure proper access rights are granted |
| 404 | Not Found | Resource does not exist | Verify endpoint URL and availability |
| 405 | Method Not Allowed | Method not supported on resource | Use allowed HTTP methods (GET, POST, etc.) |
| 406 | Not Acceptable | Unacceptable content type requested | Modify Accept header or response format |
| 407 | Proxy Authentication Required | Authentication required for proxy | Configure proxy auth credentials |
| 408 | Request Timeout | Client took too long | Retry with improved network latency |
| 409 | Conflict | Conflict with current resource state | Resolve data duplication or sync conflict |
| 410 | Gone | Resource permanently removed | Remove links or references to the resource |
| 411 | Length Required | Missing Content-Length header |
Set correct content length in request header |
| 412 | Precondition Failed | Conditional headers not met | Update If-* headers to match server state |
| 413 | Payload Too Large | Request body exceeds size limit | Reduce payload or increase client_max_body_size in NGINX |
| 414 | URI Too Long | Request URI too long | Shorten URL or use POST method for data |
| 415 | Unsupported Media Type | Wrong content type | Use supported media types like JSON or XML |
| 416 | Range Not Satisfiable | Requested range not valid | Adjust Range header to valid range |
| 417 | Expectation Failed | Expect: header condition not met |
Remove or correct Expect: headers |
| 418 | I'm a teapot | RFC joke | Ignore or customize if used |
| 429 | Too Many Requests | Rate-limiting exceeded | Implement retry/backoff or request limit handling |
| 451 | Unavailable for Legal Reasons | Blocked due to legal policy | Follow local law or use a compliant source |
5xx: Server Errors
| Code | Meaning | Use Case | Resolution |
|---|---|---|---|
| 500 | Internal Server Error | Generic server error | Check logs; fix application/server errors |
| 501 | Not Implemented | Feature/method not supported | Avoid using unsupported methods |
| 502 | Bad Gateway | Invalid response from upstream | Check backend service, DNS, or firewall |
| 503 | Service Unavailable | Server temporarily overloaded or down | Add retries, scale backend, or show maintenance page |
| 504 | Gateway Timeout | Upstream server didn’t respond in time | Tune timeout settings or backend performance |
| 505 | HTTP Version Not Supported | Unsupported protocol version | Use HTTP/1.1 or HTTP/2 as supported |
| 507 | Insufficient Storage | No space to store resource | Clear disk space or increase quota |
| 511 | Network Auth Required | Authentication required to access network | Authenticate via network portal or gateway |