Here’s an extended list of HTTP status codes with concise descriptions:
1xx Informational
1. 100 Continue: The server received the initial part of the request and the client should continue.
2. 101 Switching Protocols: The server agrees to switch protocols as requested by the client.
3. 102 Processing (WebDAV): The server is processing the request, but no response is available yet.
4. 103 Early Hints: Used to return some response headers before the final response.
---
2xx Success
5. 200 OK: The request was successful, and the server returned the expected result.
6. 201 Created: The request succeeded, and a new resource was created.
7. 202 Accepted: The request has been accepted for processing but not completed yet.
8. 203 Non-Authoritative Information: The server returned metadata that may not match the origin server.
9. 204 No Content: The request was successful, but there's no content to send back.
10. 205 Reset Content: The request succeeded, and the client should reset the view.
11. 206 Partial Content: The server is returning part of the resource as requested (e.g., for range requests).
12. 207 Multi-Status (WebDAV): The response contains multiple status codes for different parts of the request.
13. 208 Already Reported (WebDAV): The resource was already reported earlier in the response.
14. 226 IM Used: The server successfully applied a Delta encoding.
---
3xx Redirection
15. 300 Multiple Choices: The request can be fulfilled by multiple resources; choose one.
16. 301 Moved Permanently: The requested resource has been permanently moved to a new URL.
17. 302 Found: The resource is temporarily located at a different URL.
18. 303 See Other: The client should retrieve the resource using a different URL (GET).
19. 304 Not Modified: The cached version of the resource is still valid.
20. 305 Use Proxy: The resource must be accessed through a proxy (deprecated).
21. 307 Temporary Redirect: The resource is temporarily available at a different URL, but the request method should not change.
22. 308 Permanent Redirect: The resource is permanently available at a new URL, with the same request method.
---
4xx Client Errors
23. 400 Bad Request: The server couldn't understand the request due to invalid syntax.
24. 401 Unauthorized: Authentication is required but was not provided or failed.
25. 402 Payment Required: Reserved for future use, often associated with payments.
26. 403 Forbidden: The server understands the request but refuses to authorize it.
27. 404 Not Found: The server couldn't find the requested resource.
28. 405 Method Not Allowed: The request method is not supported for the resource.
29. 406 Not Acceptable: The requested resource cannot produce a response matching the Accept headers.
30. 407 Proxy Authentication Required: Authentication is required through a proxy server.
31. 408 Request Timeout: The server timed out waiting for the client to send the request.
32. 409 Conflict: The request conflicts with the current state of the resource.
33. 410 Gone: The resource is no longer available and won't be available again.
34. 411 Length Required: The server requires the Content-Length header in the request.
35. 412 Precondition Failed: The request's preconditions were not met.
36. 413 Payload Too Large: The request payload exceeds the server's limits.
37. 414 URI Too Long: The requested URI is too long for the server to process.
38. 415 Unsupported Media Type: The request's media type is unsupported by the server.
39. 416 Range Not Satisfiable: The range specified in the request is invalid.
40. 417 Expectation Failed: The server cannot meet the expectations in the request header.
41. 418 I'm a Teapot: An April Fools’ joke code from RFC 2324 (not implemented).
42. 421 Misdirected Request: The request was directed to a server that cannot produce a response.
43. 422 Unprocessable Entity (WebDAV): The request was well-formed but cannot be processed.
44. 423 Locked (WebDAV): The resource is locked.
45. 424 Failed Dependency (WebDAV): The request failed due to a dependency on another request.
46. 425 Too Early: The server is unwilling to process a request that might be replayed.
47. 426 Upgrade Required: The client should switch to a different protocol.
48. 428 Precondition Required: The server requires the request to be conditional.
49. 429 Too Many Requests: The client has sent too many requests in a given time.
50. 431 Request Header Fields Too Large: The request header fields are too large for the server.
51. 451 Unavailable For Legal Reasons: The resource is unavailable due to legal restrictions.
---
5xx Server Errors
52. 500 Internal Server Error: The server encountered an error and couldn't complete the request.
53. 501 Not Implemented: The server doesn't support the request's functionality.
54. 502 Bad Gateway: The server acted as a gateway and received an invalid response.
55. 503 Service Unavailable: The server is temporarily unable to handle the request.
56. 504 Gateway Timeout: The server didn't receive a timely response from an upstream server.
57. 505 HTTP Version Not Supported: The server doesn't support the HTTP version used in the request.
58. 506 Variant Also Negotiates: The server has a configuration error preventing negotiation.
59. 507 Insufficient Storage (WebDAV): The server is unable to store the representation.
60. 508 Loop Detected (WebDAV): The server detected an infinite loop while processing the request.
61. 510 Not Extended: Further extensions to the request are required for it to be fulfilled.
62. 511 Network Authentication Required: Authentication is required to access the network.
---
Let me know if you'd like further explanations or examples!, This image is an informative reference displaying an extended list of HTTP status codes used in web communications. The list is organized into categories: Informational, Success, Redirection, Client Errors, and Server Errors. Each category includes specific codes along with concise descriptions of their meanings. This serves as a quick guide for developers and web professionals to understand how to diagnose issues encountered during web requests. Understanding these codes helps in troubleshooting and optimizing web interactions effectively
