Skip to main content

Project Status Codes Documentation

This document contains a list of status codes for the project along with explanations of where each error originates.

HTTP Status Codes​

1. 100 Continue ✅​

  • Description: The server has received the request headers, and the client should proceed to send the request body.
  • Possible Cause: The client has sent the initial request and is waiting for confirmation to continue.
  • Origin:
    • DevOps: Server is receiving and processing the request headers.
    • Server: Server correctly handling HTTP request headers.

2. 101 Switching Protocols 🔄​

  • Description: The server is switching protocols as requested by the client.
  • Possible Cause: The server is switching to a new protocol (e.g., WebSocket).
  • Origin:
    • DevOps: The server supports protocol switching and responds as expected.
    • Server: Server handles protocol switching.

3. 200 OK 🟢​

  • Description: The request was successful.
  • Possible Cause: Everything is working as expected.
  • Origin:
    • DevOps: Server setup is correct.
    • Server: The server is running fine and can handle requests.
    • Developers: Code logic is correct and running.
    • MySQL: Running as expected.
    • PHP: PHP is processing the request properly.
    • Node.js: Node.js is running as expected.

4. 201 Created 🟢​

  • Description: The request has been fulfilled and resulted in a new resource being created.
  • Possible Cause: Resource successfully created (e.g., new database record).
  • Origin:
    • DevOps: Server has successfully processed the request.
    • Developers: API or code logic successfully created a resource.

5. 202 Accepted ⏳​

  • Description: The request has been accepted for processing, but the processing is not complete.
  • Possible Cause: Request is queued for processing (e.g., background task).
  • Origin:
    • DevOps: Task has been accepted and is being processed asynchronously.
    • Server: Task is in a queue awaiting execution.

6. 203 Non-Authoritative Information 📂​

  • Description: The request was successful, but the returned information may be from a cached copy.
  • Possible Cause: Cache data is being used for the response.
  • Origin:
    • Server: Using cached data instead of real-time data.

7. 204 No Content 🚫​

  • Description: The server successfully processed the request, but there is no content to return.
  • Possible Cause: Request was successful but no data to return (e.g., DELETE request).
  • Origin:
    • DevOps: Server processed request and returned no content.
    • Server: No content to send in response.

8. 205 Reset Content 🔄​

  • Description: The server successfully processed the request, but the client should reset the document view.
  • Possible Cause: Request successfully completed, but the user interface needs to be reset.
  • Origin:
    • Server: Server handled the request but requires the client to reset the view.

9. 206 Partial Content 📄​

  • Description: The server is delivering only part of the resource due to a range header sent by the client.
  • Possible Cause: The client requested a specific range of data (e.g., downloading a file in chunks).
  • Origin:
    • Server: Handling partial content requests correctly.

10. 300 Multiple Choices 🔀​

  • Description: The request has more than one possible response.
  • Possible Cause: There are multiple valid responses for the request.
  • Origin:
    • DevOps: Server is correctly handling multiple routes for the request.

11. 301 Moved Permanently 🔁​

  • Description: The requested resource has been permanently moved to a new location.
  • Possible Cause: The URL has changed permanently.
  • Origin:
    • Server: URL has been redirected permanently.
    • DevOps: Proper redirection rules are in place.

12. 302 Found 🔄​

  • Description: The requested resource has been temporarily moved to a new location.
  • Possible Cause: Temporary redirect to a different resource.
  • Origin:
    • Server: Temporary redirection to another resource.
    • DevOps: Redirection for temporary use.

13. 303 See Other 🔗​

  • Description: The response to the request can be found under a different URL using a GET request.
  • Possible Cause: Redirecting to another resource using GET.
  • Origin:
    • Server: Response redirected via a GET method.
    • DevOps: Handling of multiple response types.

14. 304 Not Modified 🛑​

  • Description: The resource has not been modified since the last request.
  • Possible Cause: The cached copy is still valid.
  • Origin:
    • Server: Responded with no modifications since last retrieval.
    • DevOps: Efficient use of cache mechanisms.

15. 305 Use Proxy 🧑‍💻​

  • Description: The requested resource must be accessed through a proxy.
  • Possible Cause: The client needs to use a proxy to access the resource.
  • Origin:
    • Server: Direct access is not allowed; proxy required.
    • DevOps: Proxy settings and configurations in place.

16. 306 Switch Proxy 🔄​

  • Description: This code is no longer used. Originally meant to indicate that a proxy is to be used.
  • Possible Cause: The code was obsolete and no longer in use.
  • Origin:
    • Server: Deprecated code.
    • DevOps: Handling of outdated HTTP status codes.

17. 307 Temporary Redirect 🔄​

  • Description: The resource has been temporarily moved to a new URL, and future requests should use the original URL.
  • Possible Cause: Temporary redirection that should be reversed in future requests.
  • Origin:
    • Server: Temporary redirection.
    • DevOps: Redirection for short-term use.

18. 308 Permanent Redirect 🔁​

  • Description: The resource has been permanently moved to a new URL, and all future requests should use the new URL.
  • Possible Cause: A permanent move with future requests pointing to the new location.
  • Origin:
    • Server: Permanent redirection.
    • DevOps: Ensuring clients follow the new URL.

19. 400 Bad Request ❌​

  • Description: The request could not be understood by the server due to malformed syntax.
  • Possible Cause: Malformed request or incorrect syntax.
  • Origin:
    • Server: Server could not parse the request.
    • Developers: Issues in request format (JSON/XML).

20. 401 Unauthorized 🔒​

  • Description: The request requires user authentication.
  • Possible Cause: The user is not authenticated or their credentials are incorrect.
  • Origin:
    • Server: Authentication failed.
    • DevOps: Incorrect or missing authentication tokens.

21. 402 Payment Required 💳​

  • Description: The request cannot be processed until payment is made.
  • Possible Cause: Payment is required for further action.
  • Origin:
    • Server: Resource requires payment to proceed.
    • DevOps: Integration of payment gateways.

22. 403 Forbidden 🚫​

  • Description: The server understands the request, but it refuses to authorize it.
  • Possible Cause: User does not have permission to access the resource.
  • Origin:
    • Server: Access denied for the user.
    • DevOps: Incorrect permissions or roles set up.

23. 404 Not Found 🔍​

  • Description: The server cannot find the requested resource.
  • Possible Cause: The resource does not exist or has been moved.
  • Origin:
    • Server: Requested resource is missing.
    • DevOps: Incorrect URL or broken links.

24. 405 Method Not Allowed 🛑​

  • Description: The method specified in the request is not allowed for the resource.
  • Possible Cause: Trying to use an unsupported HTTP method (e.g., POST on a resource that only accepts GET).
  • Origin:
    • Server: The HTTP method is not allowed for the endpoint.
    • DevOps: Incorrect HTTP method used.

25. 406 Not Acceptable ❌​

  • Description: The resource is not capable of generating content acceptable according to the Accept header in the request.
  • Possible Cause: The server cannot respond in the requested format.
  • Origin:
    • Server: Unable to match requested content type.
    • DevOps: Mismatch in content negotiation.

26. 407 Proxy Authentication Required 🧑‍💻🔒​

  • Description: The client must authenticate itself with the proxy.
  • Possible Cause: The proxy requires authentication before the request can be processed.
  • Origin:
    • Server: Proxy requires credentials.
    • DevOps: Proxy authentication misconfiguration.

27. 408 Request Timeout ⏳​

  • Description: The server timed out waiting for the request.
  • Possible Cause: The server waited too long for a request and timed out.
  • Origin:
    • Server: Timeout due to inactivity.
    • DevOps: Slow request handling or network issues.

28. 409 Conflict ⚔️​

  • Description: The request could not be completed due to a conflict with the current state of the resource.
  • Possible Cause: Conflict when trying to update a resource with conflicting data.
  • Origin:
    • Server: Resource conflict (e.g., version mismatch).
    • DevOps: Concurrent modification of resources.

30. 410 Gone 🚪​

  • Description: The resource requested is no longer available and will not be available again.
  • Possible Cause: The resource has been permanently deleted or removed.
  • Origin:
    • Server: The resource is permanently gone.
    • DevOps: Deleted or moved resource without a replacement.

31. 411 Length Required 🔢​

  • Description: The server refuses to process the request without a defined Content-Length header.
  • Possible Cause: Missing or invalid Content-Length header.
  • Origin:
    • Server: Requires content length for processing.
    • DevOps: Incomplete request body.

32. 412 Precondition Failed ⚠️​

  • Description: One or more conditions in the request header fields evaluated to false.
  • Possible Cause: The request includes a header that fails a precondition check.
  • Origin:
    • Server: Precondition on the request failed.
    • DevOps: Conditional request logic issue.

33. 413 Payload Too Large 📦​

  • Description: The request is larger than the server is willing or able to process.
  • Possible Cause: The request body exceeds the maximum allowed size.
  • Origin:
    • Server: Payload is too large for processing.
    • DevOps: Large file uploads or data overflows.

34. 414 URI Too Long 🌐​

  • Description: The URI provided is too long for the server to process.
  • Possible Cause: The URL exceeds server limits for length.
  • Origin:
    • Server: URL length exceeds server limit.
    • DevOps: URL encoding or parameters issue.

35. 415 Unsupported Media Type 🎥❌​

  • Description: The server refuses to process the request because the media type is unsupported.
  • Possible Cause: The request's Content-Type is not supported.
  • Origin:
    • Server: Unsupported media type for the resource.
    • DevOps: Mismatch in media types or content type negotiation.

36. 416 Range Not Satisfiable 📏​

  • Description: The server cannot fulfill the range request because the range is outside the available data.
  • Possible Cause: The requested range does not exist in the resource.
  • Origin:
    • Server: Range exceeds available data.
    • DevOps: Incorrect range request in headers.

37. 417 Expectation Failed 🙅‍♂️​

  • Description: The server cannot meet the requirements of the Expect request header.
  • Possible Cause: The Expect header contains an expectation that the server can't satisfy.
  • Origin:
    • Server: Cannot meet expectation specified in the request.
    • DevOps: Misconfiguration of headers.

38. 418 I'm a teapot ☕​

  • Description: The server refuses to brew coffee because it is a teapot.
  • Possible Cause: This is a humorous error defined by an April Fools' Day joke (RFC 2324).
  • Origin:
    • Server: Teapot response to a brewing request.
    • DevOps: Prank or misconfigured error.

39. 421 Misdirected Request 🚧​

  • Description: The request was directed at a server that is not able to produce a response.
  • Possible Cause: The request was sent to the wrong server.
  • Origin:
    • Server: Misdirection due to incorrect endpoint.
    • DevOps: Incorrect routing or load balancing.

40. 422 Unprocessable Entity 🛠️​

  • Description: The server understands the content type of the request but cannot process the instructions.
  • Possible Cause: Invalid data or semantic errors in the request.
  • Origin:
    • Server: Unprocessable request entity.
    • DevOps: Validation or business logic failure.

41. 423 Locked 🔒​

  • Description: The resource that is being accessed is locked.
  • Possible Cause: The resource is currently locked and cannot be modified.
  • Origin:
    • Server: Resource locked for editing.
    • DevOps: File/resource locking mechanism.

42. 424 Failed Dependency ⚠️​

  • Description: The request failed due to the failure of a previous request.
  • Possible Cause: One request's failure led to the failure of another dependent request.
  • Origin:
    • Server: Dependency failure.
    • DevOps: Chained request dependencies.

43. 425 Too Early ⏳​

  • Description: The server is unwilling to process the request because it is too early.
  • Possible Cause: The server expects some delay before processing the request.
  • Origin:
    • Server: Request received too soon.
    • DevOps: Timing or rate-limiting issues.

44. 426 Upgrade Required 🔼​

  • Description: The client should switch to a different protocol, e.g., upgrading from HTTP to HTTPS.
  • Possible Cause: The client needs to upgrade its protocol version.
  • Origin:
    • Server: Required protocol upgrade.
    • DevOps: Outdated protocol or security requirements.

45. 428 Precondition Required ⚙️​

  • Description: The server requires the request to be conditional.
  • Possible Cause: The server requires specific preconditions to process the request.
  • Origin:
    • Server: Preconditions missing in request.
    • DevOps: Conditional logic missing or misconfigured.

46. 429 Too Many Requests 📉​

  • Description: The user has sent too many requests in a given amount of time.
  • Possible Cause: Rate limiting or traffic spikes.
  • Origin:
    • Server: Too many requests, rate-limited.
    • DevOps: Traffic overload or rate-limiting rules.

47. 431 Request Header Fields Too Large 📏​

  • Description: The server refuses to process the request because the request header fields are too large.
  • Possible Cause: Header size exceeds server limits.
  • Origin:
    • Server: Header field size issue.
    • DevOps: Excessive headers or cookies.

48. 451 Unavailable For Legal Reasons 📜​

  • Description: The resource is unavailable due to legal reasons.
  • Possible Cause: The requested resource is blocked or removed due to legal restrictions.
  • Origin:
    • Server: Content blocked for legal reasons.
    • DevOps: Legal restrictions or compliance issues.

49. 500 Internal Server Error 🛑​

  • Description: The server encountered an unexpected condition that prevented it from fulfilling the request.
  • Possible Cause: General server error, often a misconfiguration or server fault.
  • Origin:
    • Server: Unhandled internal error.
    • DevOps: Misconfigured server or application bug.

50. 501 Not Implemented 🔧​

  • Description: The server does not support the functionality required to fulfill the request.
  • Possible Cause: The server doesn't recognize the request method or functionality.
  • Origin:
    • Server: Method not implemented.
    • DevOps: Missing server feature or functionality.

51. 502 Bad Gateway 🚪​

  • Description: The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
  • Possible Cause: The upstream server is down or misconfigured.
  • Origin:
    • Server: Proxy/gateway communication failure.
    • DevOps: Misconfigured or failing upstream server.

52. 503 Service Unavailable 📴​

  • Description: The server is currently unable to handle the request due to temporary overloading or maintenance of the server.
  • Possible Cause: Server is down for maintenance or temporarily overloaded.
  • Origin:
    • Server: Overloaded or under maintenance.
    • DevOps: Server scaling issues, scheduled maintenance.

53. 504 Gateway Timeout ⏱️​

  • Description: The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server or some other auxiliary server.
  • Possible Cause: The server timed out waiting for a response from an upstream server.
  • Origin:
    • Server: Timeout waiting for upstream.
    • DevOps: Network issues or upstream latency.

54. 505 HTTP Version Not Supported 🧰​

  • Description: The server does not support the HTTP protocol version that was used in the request.
  • Possible Cause: Incompatible HTTP version used in the request.
  • Origin:
    • Server: Unsupported HTTP version.
    • DevOps: Outdated HTTP version or misconfiguration.

55. 506 Variant Also Negotiates 🔄​

  • Description: The server has an internal configuration error: transparent content negotiation for the request results in a circular reference.
  • Possible Cause: Misconfigured server causing infinite loops in content negotiation.
  • Origin:
    • Server: Configuration error in content negotiation.
    • DevOps: Misconfigured server settings or negotiation loops.

56. 507 Insufficient Storage 💾​

  • Description: The server is unable to store the representation needed to complete the request.
  • Possible Cause: Server storage is full or insufficient.
  • Origin:
    • Server: Insufficient disk space or resources.
    • DevOps: Storage capacity exceeded or full server.

57. 508 Loop Detected 🔄​

  • Description: The server detected an infinite loop while processing a request.
  • Possible Cause: Circular references in the request or configuration.
  • Origin:
    • Server: Infinite loop detected in processing.
    • DevOps: Misconfiguration causing recursive loops.

58. 510 Not Extended 🔓​

  • Description: Further extensions to the request are required for the server to fulfill it.
  • Possible Cause: Additional extensions required to process the request.
  • Origin:
    • Server: Request lacks necessary extensions.
    • DevOps: Missing feature or protocol extension.

59. 511 Network Authentication Required 🔒​

  • Description: The client needs to authenticate to gain network access.
  • Possible Cause: The client must authenticate before accessing the network.
  • Origin:
    • Server: Network authentication required.
    • DevOps: Authentication configuration needed.

60. 599 Network Connect Timeout Error ⌛​

  • Description: The server encountered a timeout while attempting to connect to the network.
  • Possible Cause: Network connection timeout when the server attempts to connect to another network resource.
  • Origin:
    • Server: Network connection timeout.
    • DevOps: Network latency or connection issues.

61. 600 Unparseable Response Headers 🤔​

  • Description: The response headers could not be parsed by the client due to malformed or unrecognizable formatting.
  • Possible Cause: The server sent an invalid response format.
  • Origin:
    • Server: Malformed response headers.
    • DevOps: Misconfigured server sending invalid headers.

62. 601 Request Denied ❌​

  • Description: The server has understood the request, but it refuses to authorize it.
  • Possible Cause: The server is intentionally blocking access to the requested resource.
  • Origin:
    • Server: Unauthorized access.
    • DevOps: Access control or firewall issues.

63. 602 Proxy Declined Request 🚫​

  • Description: The proxy server declined to handle the request.
  • Possible Cause: The proxy server refused to process the request due to internal issues.
  • Origin:
    • Server: Proxy configuration error or refusal.
    • DevOps: Proxy setup issues.

64. 603 Invalid Cache Operation 💡​

  • Description: The cache operation was invalid or unsupported by the server.
  • Possible Cause: The server doesn't support the cache operation requested.
  • Origin:
    • Server: Invalid cache operation request.
    • DevOps: Cache misconfiguration or unsupported feature.

65. 604 DNS Lookup Failure 🌐​

  • Description: The server encountered an error during the DNS lookup process.
  • Possible Cause: The domain name could not be resolved.
  • Origin:
    • Server: DNS resolution failure.
    • DevOps: DNS misconfiguration or external DNS issue.

66. 605 Connection Rejected 🔒​

  • Description: The connection to the server was rejected, typically due to server rules.
  • Possible Cause: The server rejected the connection attempt due to rules or load balancing configurations.
  • Origin:
    • Server: Rejected connection attempt.
    • DevOps: Misconfigured load balancer or server rejection.
  • Description: The requested resource is unavailable due to legal restrictions or compliance issues.
  • Possible Cause: Access to the resource is blocked for legal or regulatory reasons.
  • Origin:
    • Server: Resource blocked due to legal reasons.
    • DevOps: Legal compliance issues or restrictions.

68. 607 Operation Timed Out ⏳​

  • Description: The operation on the server has timed out.
  • Possible Cause: A long-running request failed due to timeout constraints.
  • Origin:
    • Server: Request timeout exceeded.
    • DevOps: Network latency or inefficient server processing.

69. 608 Network Unreachable 🌍​

  • Description: The network is unreachable, and the server cannot be contacted.
  • Possible Cause: The server's network is down or disconnected.
  • Origin:
    • Server: Network issues or server disconnection.
    • DevOps: Server network misconfiguration or outage.

70. 609 Unauthorized Request 🚷​

  • Description: The server recognized the request but is refusing to process it due to missing or invalid authentication.
  • Possible Cause: The request lacks the proper credentials or the credentials are invalid.
  • Origin:
    • Server: Authentication failure.
    • DevOps: Authentication misconfiguration or missing credentials.

71. 610 Bad Request Format 📛​

  • Description: The format of the request is incorrect or not supported by the server.
  • Possible Cause: Incorrectly formatted request headers or body.
  • Origin:
    • Server: Malformed request syntax.
    • DevOps: Improper request formatting.

72. 611 Unrecognized Query Parameter 🔍​

  • Description: The server does not recognize one or more of the query parameters in the request.
  • Possible Cause: A request with unknown or unsupported query parameters.
  • Origin:
    • Server: Invalid query parameters.
    • DevOps: Incorrect API query or route parameters.

73. 612 Dependency Timeout ⏰​

  • Description: The request failed because of a timeout in an external dependency.
  • Possible Cause: Timeout in a downstream service or external system.
  • Origin:
    • Server: Dependent service failure or timeout.
    • DevOps: Dependent API or service misconfiguration.

74. 613 Response Too Large 📂​

  • Description: The response from the server is too large to process.
  • Possible Cause: The server sent an unusually large response body.
  • Origin:
    • Server: Response body exceeds size limits.
    • DevOps: Unoptimized data retrieval or API response size.

75. 614 Invalid Authentication Token 🔑​

  • Description: The authentication token used in the request is invalid or expired.
  • Possible Cause: The token is either malformed or no longer valid.
  • Origin:
    • Server: Invalid or expired token.
    • DevOps: Token handling or renewal issues.

76. 615 Unsupported Media Type 📸​

  • Description: The server does not support the media type of the requested resource.
  • Possible Cause: The request content type is not supported by the server.
  • Origin:
    • Server: Unsupported content type.
    • DevOps: Incorrect Content-Type header or data format.

77. 616 Resource Locked 🔒​

  • Description: The requested resource is locked and cannot be modified or accessed.
  • Possible Cause: The resource is currently in use and locked by another process.
  • Origin:
    • Server: Resource lock conflict.
    • DevOps: Resource management or access control issues.

78. 617 Resource Expired ⏳​

  • Description: The requested resource has expired and is no longer accessible.
  • Possible Cause: Expired tokens, sessions, or cached content.
  • Origin:
    • Server: Expired resource.
    • DevOps: Expired session or cache timeout.

79. 618 Temporary Redirect 🔄​

  • Description: The resource has been temporarily redirected to another location.
  • Possible Cause: The server temporarily redirects the client to another URI.
  • Origin:
    • Server: Temporary redirect setup.
    • DevOps: Redirect configuration or routing setup.

80. 619 Unsupported Protocol Version 🛠​

  • Description: The server does not support the version of the protocol used in the request.
  • Possible Cause: Request made using an outdated or unsupported protocol version.
  • Origin:
    • Server: Unsupported protocol version.
    • DevOps: Outdated protocol version or mismatch.

81. 620 Resource Not Available 🛑​

  • Description: The requested resource is temporarily unavailable and cannot be accessed at the moment.
  • Possible Cause: Server resources are temporarily unavailable.
  • Origin:
    • Server: Resource is currently unavailable.
    • DevOps: Maintenance or downtime.

82. 621 Custom Error 🚫​

  • Description: A custom error defined by the server that doesn't fall under a standard HTTP status code.
  • Possible Cause: Specific business or application logic error.
  • Origin:
    • Server: Custom error logic.
    • DevOps: Custom error handling implementation.

83. 622 Invalid Query Request 📋​

  • Description: The query format in the request is invalid or not recognized.
  • Possible Cause: A malformed or unrecognized query string.
  • Origin:
    • Server: Invalid query format.
    • DevOps: Query string errors or unsupported queries.

84. 623 Authentication Failed 🔐​

  • Description: The authentication credentials provided were incorrect or failed verification.
  • Possible Cause: Invalid username or password.
  • Origin:
    • Server: Authentication failure.
    • DevOps: Incorrect authentication handling.

85. 624 Insufficient Storage 💾​

  • Description: The server does not have enough storage to fulfill the request.
  • Possible Cause: Server or system storage capacity exceeded.
  • Origin:
    • Server: Storage limit reached.
    • DevOps: Insufficient disk space or data overflow.

86. 625 Unsuccessful Dependent Request 🔗​

  • Description: A request failed because it depends on another request or service that failed.
  • Possible Cause: Dependency or chained request failure.
  • Origin:
    • Server: Failed dependency.
    • DevOps: Broken service dependencies.

87. 626 Rate Limit Exceeded ⚠️​

  • Description: The client has exceeded the allowed rate limit for requests.
  • Possible Cause: Too many requests sent within a specified time.
  • Origin:
    • Server: Exceeded rate limit.
    • DevOps: Misconfigured API rate limiting.

88. 627 Invalid Session 🔄​

  • Description: The session identifier is invalid, expired, or could not be found.
  • Possible Cause: Session ID is invalid or expired.
  • Origin:
    • Server: Invalid session state.
    • DevOps: Session timeout or mismanagement.

89. 628 Conflicting Updates 🔄​

  • Description: There was a conflict between simultaneous updates or requests to the same resource.
  • Possible Cause: Simultaneous updates to the same resource causing conflict.
  • Origin:
    • Server: Conflict due to concurrent requests.
    • DevOps: Resource locking or concurrency issues.

90. 629 Resource Deleted 🚮​

  • Description: The requested resource has been permanently deleted and is no longer available.
  • Possible Cause: The resource has been removed or purged from the system.
  • Origin:
    • Server: Resource deletion.
    • DevOps: Resource removal or data purging.

91. 630 Connection Timeout ⏳​

  • Description: The request timed out while trying to establish a connection with the server.
  • Possible Cause: Network issues or slow server response.
  • Origin:
    • Server: Connection issues or server not responding.
    • DevOps: Network congestion or misconfigured timeout settings.

92. 631 Unknown Error 🧐​

  • Description: An unknown error occurred that doesn't fit any standard status code.
  • Possible Cause: Unexpected or unclassified error during processing.
  • Origin:
    • Server: Internal server error with no specific cause.
    • DevOps: Generic system failure.

93. 632 Invalid Token 🛑​

  • Description: The token provided in the request is invalid, expired, or malformed.
  • Possible Cause: Invalid or expired authorization token.
  • Origin:
    • Server: Invalid authentication token.
    • DevOps: Token mismanagement or expiration.

94. 633 Dependency Timeout ⏳​

  • Description: A dependent service request timed out and could not complete successfully.
  • Possible Cause: Timeout during service dependency request.
  • Origin:
    • Server: Dependent service timeout.
    • DevOps: Service failure or misconfigured dependency timeout.

95. 634 Request Conflict ⚠️​

  • Description: There was a conflict in the request that prevents it from being processed.
  • Possible Cause: Conflicting operations or requests submitted simultaneously.
  • Origin:
    • Server: Request conflict detected.
    • DevOps: Simultaneous resource modifications or misconfigured request handling.

96. 635 Duplicate Request 🔁​

  • Description: The request is a duplicate and has already been processed.
  • Possible Cause: Repeated submission of the same request.
  • Origin:
    • Server: Duplicate request detected.
    • DevOps: Redundant API calls or retries.

97. 636 Too Many Connections 🌐​

  • Description: The server is experiencing too many simultaneous connections.
  • Possible Cause: Overload due to excessive client connections.
  • Origin:
    • Server: Max connections limit exceeded.
    • DevOps: Server overload or connection pool exhaustion.

98. 637 Service Temporarily Unavailable ⏸️​

  • Description: The service is temporarily unavailable, usually due to maintenance or server overload.
  • Possible Cause: Scheduled maintenance or unexpected overload.
  • Origin:
    • Server: Service unavailable.
    • DevOps: Maintenance mode or service failure.

99. 638 Invalid API Key 🔑​

  • Description: The API key provided is invalid or has expired.
  • Possible Cause: Invalid or expired key for accessing the API.
  • Origin:
    • Server: Invalid or expired API key.
    • DevOps: API key mismanagement.

100. 639 Unauthorized Access 🔓​

  • Description: The client is not authorized to access the requested resource.
  • Possible Cause: Missing or incorrect authorization credentials.
  • Origin:
    • Server: Authorization failure.
    • DevOps: Misconfigured permissions or missing credentials.

101. 640 Service Unavailable 📴​

  • Description: The service is unavailable due to maintenance or overload.
  • Possible Cause: Server maintenance or excessive traffic.
  • Origin:
    • Server: Service unavailable.
    • DevOps: Maintenance or overcapacity issues.

102. 641 Bad Request Format 📚​

  • Description: The format of the request is not supported by the server.
  • Possible Cause: Malformed request or incorrect syntax.
  • Origin:
    • Server: Invalid request format.
    • DevOps: Invalid request payload.

103. 642 Rate Limit Exceeded 🛑​

  • Description: The request has been rate-limited due to too many requests in a given timeframe.
  • Possible Cause: Excessive number of requests within a short period.
  • Origin:
    • Server: Rate-limiting exceeded.
    • DevOps: API rate-limiting policies.

104. 643 Feature Not Supported 📴​

  • Description: The requested feature is not supported by the server or API.
  • Possible Cause: Requested feature or endpoint is unavailable.
  • Origin:
    • Server: Feature not available.
    • DevOps: Unsupported functionality.

105. 644 Too Many Requests 🌀​

  • Description: The client has sent too many requests in a short period.
  • Possible Cause: Exceeding the maximum number of requests allowed.
  • Origin:
    • Server: Too many requests in a short time.
    • DevOps: Request throttling or rate-limiting.

106. 645 Connection Refused 🚫​

  • Description: The server refused the connection attempt.
  • Possible Cause: Server rejecting incoming connections.
  • Origin:
    • Server: Connection rejected.
    • DevOps: Firewall or connection restrictions.

107. 646 Invalid Request Body 📜​

  • Description: The body of the request is invalid or does not conform to the expected format.
  • Possible Cause: Incorrect request body format or missing required fields.
  • Origin:
    • Server: Invalid body structure.
    • DevOps: Request body validation failure.

108. 647 Authentication Failed ❌​

  • Description: Authentication failed due to incorrect credentials.
  • Possible Cause: Invalid login credentials or authentication token.
  • Origin:
    • Server: Authentication failure.
    • DevOps: Invalid user credentials or token.

109. 648 Server Rebooting 🔄​

  • Description: The server is rebooting and cannot process the request at the moment.
  • Possible Cause: System maintenance or unplanned reboot.
  • Origin:
    • Server: Server reboot in progress.
    • DevOps: Reboot or restart for updates.

110. 649 Insufficient Permissions 🚫​

  • Description: The user does not have the necessary permissions to access the requested resource.
  • Possible Cause: Insufficient access rights.
  • Origin:
    • Server: Access denied due to permissions.
    • DevOps: Misconfigured user roles or permission

111. 650 Proxy Authentication Required 🔑​

  • Description: Proxy server requires authentication before the request can be processed.
  • Possible Cause: Proxy server needs credentials to forward the request.
  • Origin:
    • Server: Proxy authentication failure.
    • DevOps: Misconfigured proxy settings.

112. 651 Gateway Timeout ⏳​

  • Description: The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
  • Possible Cause: Upstream server timeout or connectivity issues.
  • Origin:
    • Server: Timeout in communication with upstream server.
    • DevOps: Network or server latency issues.

113. 652 Unauthorized Access 🔒​

  • Description: The client does not have permission to access the requested resource.
  • Possible Cause: Missing or incorrect authorization.
  • Origin:
    • Server: Denied access due to lack of authorization.
    • DevOps: Authorization failure or role misconfiguration.

114. 653 Session Expired ⏰​

  • Description: The user's session has expired and needs to be re-authenticated.
  • Possible Cause: Session timeout or cookie expiration.
  • Origin:
    • Server: Session expired.
    • DevOps: Session management issues.

115. 654 Conflict 🛠️​

  • Description: The request could not be completed due to a conflict with the current state of the resource.
  • Possible Cause: Conflicting data or resource state.
  • Origin:
    • Server: Conflict in data or resource state.
    • DevOps: Data integrity issues or concurrent access conflicts.

116. 655 Payload Too Large 🏋️​

  • Description: The request payload is too large for the server to process.
  • Possible Cause: Request body exceeds server’s allowed size.
  • Origin:
    • Server: Request body too large.
    • DevOps: Increase maximum request size.

117. 656 Invalid Token 🎫​

  • Description: The provided token is invalid or expired.
  • Possible Cause: Expired or tampered authentication token.
  • Origin:
    • Server: Invalid or expired token.
    • DevOps: Token expiration or integrity failure.

118. 657 Unprocessable Entity 🧩​

  • Description: The server understands the content type of the request but was unable to process the contained instructions.
  • Possible Cause: Semantic errors in the request.
  • Origin:
    • Server: Invalid entity data.
    • DevOps: Data validation failure.

119. 658 Too Many Redirects 🔄🔁​

  • Description: The request has resulted in too many redirects, indicating a possible infinite redirect loop.
  • Possible Cause: Misconfigured redirect rules.
  • Origin:
    • Server: Infinite or excessive redirect loops.
    • DevOps: Misconfigured URL forwarding rules.

120. 659 Unauthenticated Request 🚷​

  • Description: The request requires user authentication, but no valid credentials were provided.
  • Possible Cause: Missing or invalid authentication credentials.
  • Origin:
    • Server: Authentication credentials missing.
    • DevOps: Lack of proper authentication headers.

121. 660 Insufficient Storage 📦​

  • Description: The server is unable to store the representation needed to complete the request.
  • Possible Cause: Insufficient storage space on the server.
  • Origin:
    • Server: Storage limit exceeded.
    • DevOps: Disk space issues on server.

122. 661 Not Implemented 🛠️​

  • Description: The server does not support the functionality required to fulfill the request.
  • Possible Cause: Feature or functionality is not available on the server.
  • Origin:
    • Server: Feature not implemented.
    • DevOps: Missing feature or endpoint.

123. 662 Too Many Requests 🚶‍♂️🚶‍♀️​

  • Description: The user has sent too many requests in a given amount of time.
  • Possible Cause: Rate limiting exceeded.
  • Origin:
    • Server: Rate limit exceeded.
    • DevOps: Misconfigured rate-limiting settings.

124. 663 Not Acceptable 🚫​

  • Description: The server cannot produce a response matching the list of acceptable values defined in the request’s headers.
  • Possible Cause: Content type mismatch.
  • Origin:
    • Server: Content not acceptable based on headers.
    • DevOps: Misconfigured content negotiation.

125. 664 Precondition Failed ⛔​

  • Description: One or more conditions specified in the request header fields were evaluated as false when testing the request.
  • Possible Cause: Condition failures in the request.
  • Origin:
    • Server: Request condition failed.
    • DevOps: Condition mismatch or invalid headers.

126. 665 Locked 🔒🔑​

  • Description: The resource that is being accessed is locked and cannot be modified.
  • Possible Cause: Resource locked by another process or user.
  • Origin:
    • Server: Resource locked.
    • DevOps: Concurrency control issue.

127. 666 Failed Dependency ⚡​

  • Description: The request could not be completed due to the failure of a previous request on which it depends.
  • Possible Cause: Dependency failure.
  • Origin:
    • Server: Dependent resource failed.
    • DevOps: Service dependency failure.
  • Description: The resource requested is unavailable for legal reasons.
  • Possible Cause: Legal restrictions on resource access.
  • Origin:
    • Server: Legal blockage of resource.
    • DevOps: Legal compliance issue.

129. 668 Upstream Timeout ⏳​

  • Description: The upstream server failed to send a response within the allowed time frame.
  • Possible Cause: Timeout while waiting for an upstream server.
  • Origin:
    • Server: Timeout in upstream server.
    • DevOps: Network latency or server configuration issue.

130. 669 Internal Server Error 🛑​

  • Description: An unexpected condition was encountered and the server cannot fulfill the request.
  • Possible Cause: General server error or misconfiguration.
  • Origin:
    • Server: Unexpected internal server issue.
    • DevOps: Misconfiguration or server failure.

131. 670 Service Unavailable 🚫​

  • Description: The server is currently unable to handle the request due to temporary overloading or maintenance of the server.
  • Possible Cause: Server downtime or heavy load.
  • Origin:
    • Server: Server under heavy load.
    • DevOps: Maintenance or scaling issues.

132. 671 Gateway Timeout ⏳​

  • Description: The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server or some other auxiliary server it needed to access in order to complete the request.
  • Possible Cause: Timeout while waiting for an upstream server.
  • Origin:
    • Server: Gateway timeout.
    • DevOps: Network or upstream server failure.

133. 672 HTTP Version Not Supported 🌐​

  • Description: The server does not support the HTTP protocol version that was used in the request.
  • Possible Cause: Incompatible HTTP version.
  • Origin:
    • Server: HTTP version mismatch.
    • DevOps: Misconfigured HTTP version.

134. 673 Bandwidth Limit Exceeded 🌐🚫​

  • Description: The bandwidth limit for the requested resource has been exceeded.
  • Possible Cause: Exceeding the data transfer limits.
  • Origin:
    • Server: Bandwidth limit exceeded.
    • DevOps: Network configuration issue.

135. 674 Connection Closed Without Response ❌​

  • Description: The server closed the connection before sending a response.
  • Possible Cause: Abrupt termination of the connection.
  • Origin:
    • Server: Unexpected connection closure.
    • DevOps: Network or proxy misconfiguration.

136. 675 Retry With ⏩​

  • Description: The server is suggesting that the client should retry the request with different parameters or settings.
  • Possible Cause: Suggestion for retrying with modified settings.
  • Origin:
    • Server: Retry request with modifications.
    • DevOps: Request recommendation for adjustment.

137. 676 Unprocessable Entity 📉​

  • Description: The request was well-formed, but the server was unable to process the contained instructions.
  • Possible Cause: Invalid data format or logic.
  • Origin:
    • Server: Entity cannot be processed.
    • DevOps: Invalid or corrupt data in the request.

138. 677 Conflict 🔄​

  • Description: The request could not be completed due to a conflict with the current state of the resource.
  • Possible Cause: Conflict with existing resource.
  • Origin:
    • Server: Resource conflict detected.
    • DevOps: Concurrency issue or conflicting changes.

139. 678 Gone 🚷​

  • Description: The resource requested is no longer available at the server and no forwarding address is known.
  • Possible Cause: Resource permanently deleted or moved.
  • Origin:
    • Server: Resource no longer available.
    • DevOps: Resource deleted or moved.

140. 679 Payment Required 💳​

  • Description: The request cannot be processed because the client has not paid for the service.
  • Possible Cause: Payment required for continued service.
  • Origin:
    • Server: Payment required for request processing.
    • DevOps: Payment failure or pending transaction.

141. 680 Precondition Failed ⚠️​

  • Description: The server did not meet one of the preconditions specified by the client in the request.
  • Possible Cause: Missing or incorrect preconditions in the request.
  • Origin:
    • Server: Precondition failure.
    • DevOps: Incorrect request preconditions.

142. 681 Request Entity Too Large 📊​

  • Description: The request is larger than the server is willing or able to process.
  • Possible Cause: Request body exceeds server limits.
  • Origin:
    • Server: Large request body.
    • DevOps: Misconfigured request size limits.

143. 682 Service Temporarily Overloaded ⚠️​

  • Description: The server is currently unable to handle the request due to temporary overload or maintenance.
  • Possible Cause: Server experiencing temporary overload.
  • Origin:
    • Server: Service overload.
    • DevOps: Scaling issue or heavy traffic.

144. 683 Invalid API Key 🔑​

  • Description: The provided API key is invalid or expired.
  • Possible Cause: Invalid or expired API key.
  • Origin:
    • Server: Invalid API key.
    • DevOps: Key mismanagement or expiration.

145. 684 Too Many Requests 🛑​

  • Description: The client has sent too many requests in a given amount of time, and the server is rate-limiting the requests.
  • Possible Cause: Request rate exceeds limit.
  • Origin:
    • Server: Rate-limiting triggered.
    • DevOps: Excessive requests sent by client.

146. 685 Failed Dependency ⛔​

  • Description: The request failed because it depended on another request that failed.
  • Possible Cause: Failed dependent request.
  • Origin:
    • Server: Dependent resource failure.
    • DevOps: Unmet request dependency.

147. 686 Unauthorized Access 🚫​

  • Description: The request requires authentication and the client is not authorized.
  • Possible Cause: Authentication required or invalid credentials.
  • Origin:
    • Server: Unauthorized access.
    • DevOps: Missing or incorrect authentication.

148. 687 Insufficient Storage 💾​

  • Description: The server is unable to store the representation needed to complete the request.
  • Possible Cause: Insufficient server storage capacity.
  • Origin:
    • Server: Insufficient disk space.
    • DevOps: Storage capacity exceeded.

149. 688 Temporary Redirect 🔄​

  • Description: The resource has been temporarily moved to a different URI, and the client should use the new URI for this request.
  • Possible Cause: Temporary resource redirection.
  • Origin:
    • Server: Resource temporarily relocated.
    • DevOps: URL redirection.

150. 689 Misdirected Request 🔀​

  • Description: The request was directed at the wrong server.
  • Possible Cause: Request sent to the wrong destination server.
  • Origin:
    • Server: Incorrect destination.
    • DevOps: Misconfigured routing or DNS.

Project Status Codes Documentation (Part 16)

151. 690 Loop Detected 🔁​

  • Description: The server detected an infinite loop while processing the request.
  • Possible Cause: Circular redirection or resource loop.
  • Origin:
    • Server: Infinite loop detected.
    • DevOps: Misconfigured redirections or resources.

152. 691 Not Extended ⛔​

  • Description: The server requires further extensions to fulfill the request.
  • Possible Cause: Missing server extensions or unsupported features.
  • Origin:
    • Server: Missing functionality or extension.
    • DevOps: Incomplete server configuration.

153. 692 Network Authentication Required 🔐​

  • Description: The client must authenticate to access the network, but it hasn't done so yet.
  • Possible Cause: Network-level authentication is required.
  • Origin:
    • Server: Authentication required for network access.
    • DevOps: Lack of network authentication setup.

154. 693 Invalid Method 🛑​

  • Description: The method specified in the request is not allowed for the resource.
  • Possible Cause: Unsupported HTTP method used.
  • Origin:
    • Server: Invalid HTTP method.
    • DevOps: Misconfigured API or resource.

155. 694 Request Header Fields Too Large 📏​

  • Description: The size of the request header fields exceeds the server's limit.
  • Possible Cause: Header fields exceed the maximum size.
  • Origin:
    • Server: Header fields too large.
    • DevOps: Large cookies or header fields.

156. 695 Too Many Connections ⚡​

  • Description: The server has reached the maximum number of simultaneous connections.
  • Possible Cause: Connection limit exceeded.
  • Origin:
    • Server: Maximum connection limit.
    • DevOps: Excessive simultaneous connections.

157. 696 Connection Timeout 🕑​

  • Description: The server took too long to respond to the client’s request.
  • Possible Cause: Slow server response or network latency.
  • Origin:
    • Server: Slow response time.
    • DevOps: Network latency or server overload.

158. 697 Upgrade Required 🔄​

  • Description: The client must switch to a different protocol to complete the request.
  • Possible Cause: Protocol upgrade required.
  • Origin:
    • Server: Protocol upgrade needed.
    • DevOps: Outdated protocol version.

159. 698 Network Unreachable 🌐​

  • Description: The network is unreachable, and the request could not be completed.
  • Possible Cause: Network connection failure.
  • Origin:
    • Server: Network not available.
    • DevOps: Network misconfiguration or outage.

160. 699 Proxy Authentication Required 🔐​

  • Description: The client must authenticate with the proxy before the request can be completed.
  • Possible Cause: Proxy authentication required.
  • Origin:
    • Server: Proxy authentication needed.
    • DevOps: Proxy misconfiguration.