{"id":27201364,"url":"https://github.com/nomadicmehul/http-status-codes","last_synced_at":"2026-02-02T05:03:43.175Z","repository":{"id":261368398,"uuid":"884103895","full_name":"nomadicmehul/HTTP-Status-Codes","owner":"nomadicmehul","description":"This document provides a full list of HTTP status codes. Each code includes an explanation and a use case for better understanding.","archived":false,"fork":false,"pushed_at":"2024-11-06T06:30:50.000Z","size":6,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-06-18T10:53:08.680Z","etag":null,"topics":["error","errorcode","http","http-client","http-requests","http-server","https"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nomadicmehul.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-11-06T06:30:02.000Z","updated_at":"2024-11-06T06:31:58.000Z","dependencies_parsed_at":"2024-11-06T07:30:19.788Z","dependency_job_id":"a5bd46c0-49c7-4606-a586-a5c7fb8b530d","html_url":"https://github.com/nomadicmehul/HTTP-Status-Codes","commit_stats":null,"previous_names":["nomadicmehul/http-status-codes"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/nomadicmehul/HTTP-Status-Codes","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nomadicmehul%2FHTTP-Status-Codes","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nomadicmehul%2FHTTP-Status-Codes/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nomadicmehul%2FHTTP-Status-Codes/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nomadicmehul%2FHTTP-Status-Codes/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nomadicmehul","download_url":"https://codeload.github.com/nomadicmehul/HTTP-Status-Codes/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nomadicmehul%2FHTTP-Status-Codes/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29006081,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-02T04:25:24.522Z","status":"ssl_error","status_checked_at":"2026-02-02T04:24:51.069Z","response_time":58,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["error","errorcode","http","http-client","http-requests","http-server","https"],"created_at":"2025-04-09T21:56:29.060Z","updated_at":"2026-02-02T05:03:43.156Z","avatar_url":"https://github.com/nomadicmehul.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# HTTP Status Codes\n\nThis document provides a full list of HTTP status codes. Each code includes an explanation and a use case for better understanding.\n\n---\n\n## Table of Contents\n1. [Informational Responses (100–199)](#informational-responses-100-199)\n2. [Successful Responses (200–299)](#successful-responses-200-299)\n3. [Redirection Messages (300–399)](#redirection-messages-300-399)\n4. [Client Error Responses (400–499)](#client-error-responses-400-499)\n5. [Server Error Responses (500–599)](#server-error-responses-500-599)\n\n---\n\n## 1. Informational Responses (100–199)\n\n### 100 Continue\n- **Description**: Indicates that the initial part of a request has been received and the client can continue.\n- **Example**: Client uploads a large file and receives `100 Continue`, signaling it to send the remaining data.\n\n### 101 Switching Protocols\n- **Description**: Server is switching protocols as requested by the client.\n- **Example**: A client requests an upgrade from HTTP to WebSocket for real-time communication.\n\n### 102 Processing (WebDAV)\n- **Description**: Server is processing a WebDAV request but has not completed it.\n- **Example**: Complex WebDAV request for a file search receives `102 Processing` to avoid timeouts.\n\n### 103 Early Hints\n- **Description**: Used to pre-load resources before the final response is ready.\n- **Example**: Server sends `103 Early Hints` to preload CSS and images for a page.\n\n---\n\n## 2. Successful Responses (200–299)\n\n### 200 OK\n- **Description**: Request was successful, and the response contains the requested data.\n- **Example**: A browser loads a webpage or an API fetch request returns successfully.\n\n### 201 Created\n- **Description**: Resource was successfully created.\n- **Example**: A new user account created after form submission.\n\n### 202 Accepted\n- **Description**: Request accepted for processing, but not yet completed.\n- **Example**: Report generation request in a system that processes it in the background.\n\n### 203 Non-Authoritative Information\n- **Description**: Request successful, but response is from a cached or third-party source.\n- **Example**: Proxy server returns cached content without directly fetching the latest data.\n\n### 204 No Content\n- **Description**: Request was successful but there is no content to return.\n- **Example**: User updates profile settings, and the server acknowledges without additional data.\n\n### 205 Reset Content\n- **Description**: Client should reset the view.\n- **Example**: After submitting data, a form resets for new entries.\n\n### 206 Partial Content\n- **Description**: Partial response for a range request.\n- **Example**: Resuming a paused video or file download from a specific byte range.\n\n### 207 Multi-Status (WebDAV)\n- **Description**: Conveys multiple status codes for multiple independent operations.\n- **Example**: WebDAV requests return multiple statuses for each sub-operation on files.\n\n### 208 Already Reported (WebDAV)\n- **Description**: Used to avoid reporting the same resource multiple times.\n- **Example**: WebDAV responses that include previously processed elements.\n\n### 226 IM Used\n- **Description**: Server fulfilled a GET request with the instance manipulations applied.\n- **Example**: A response indicating a resource has been manipulated (e.g., compressed) before delivery.\n\n---\n\n## 3. Redirection Messages (300–399)\n\n### 300 Multiple Choices\n- **Description**: Indicates multiple options for the resource.\n- **Example**: User can choose between multiple file formats or language versions.\n\n### 301 Moved Permanently\n- **Description**: Resource has a new permanent URL.\n- **Example**: Permanently moved page, updating search engines and bookmarks.\n\n### 302 Found\n- **Description**: Temporary redirect to another resource.\n- **Example**: Redirect to a login page from a protected resource.\n\n### 303 See Other\n- **Description**: Redirects to a different resource using GET.\n- **Example**: Redirect to a receipt page after submitting a purchase order.\n\n### 304 Not Modified\n- **Description**: Indicates cached content is up to date.\n- **Example**: Browser cache check for an image returns `304` if unchanged.\n\n### 305 Use Proxy (Deprecated)\n- **Description**: Requested resource must be accessed through a proxy.\n- **Example**: Deprecated in HTTP/1.1 due to security concerns.\n\n### 306 (Unused)\n- **Description**: Previously reserved, but not used.\n\n### 307 Temporary Redirect\n- **Description**: Similar to `302` but method remains the same.\n- **Example**: Temporarily redirects a POST request without changing method.\n\n### 308 Permanent Redirect\n- **Description**: Similar to `301` but method remains the same.\n- **Example**: API endpoint moved permanently; clients should update the URI.\n\n---\n\n## 4. Client Error Responses (400–499)\n\n### 400 Bad Request\n- **Description**: The server could not understand the request.\n- **Example**: Malformed JSON payload in an API request.\n\n### 401 Unauthorized\n- **Description**: Authentication is required but missing or invalid.\n- **Example**: API request without a valid authentication token.\n\n### 402 Payment Required (Experimental)\n- **Description**: Reserved for future use regarding digital payment.\n- **Example**: Possible future status for subscription services.\n\n### 403 Forbidden\n- **Description**: Client has no access rights to the content.\n- **Example**: Unauthorized user attempts access to an admin-only page.\n\n### 404 Not Found\n- **Description**: Server cannot find the requested resource.\n- **Example**: Request for a non-existent webpage.\n\n### 405 Method Not Allowed\n- **Description**: HTTP method is not allowed for the requested resource.\n- **Example**: DELETE request to a read-only endpoint.\n\n### 406 Not Acceptable\n- **Description**: Content does not match client’s Accept headers.\n- **Example**: Client requests XML, but only JSON is available.\n\n### 407 Proxy Authentication Required\n- **Description**: Proxy authentication required.\n- **Example**: Request through a corporate proxy without credentials.\n\n### 408 Request Timeout\n- **Description**: Server timed out waiting for the request.\n- **Example**: Slow internet connection causes a timeout.\n\n### 409 Conflict\n- **Description**: Request conflicts with server state.\n- **Example**: Concurrent updates to a document in a collaborative app.\n\n### 410 Gone\n- **Description**: Resource permanently removed.\n- **Example**: Deprecated API endpoint.\n\n### 411 Length Required\n- **Description**: Content-Length header is missing.\n- **Example**: POST request without specifying content length.\n\n### 412 Precondition Failed\n- **Description**: Preconditions in headers not met.\n- **Example**: Conditional update request fails due to modified data.\n\n### 413 Payload Too Large\n- **Description**: Payload exceeds server limits.\n- **Example**: File upload exceeds max upload size.\n\n### 414 URI Too Long\n- **Description**: URI is too long for the server to process.\n- **Example**: Too many parameters in a GET request.\n\n### 415 Unsupported Media Type\n- **Description**: Unsupported content format.\n- **Example**: Server receives an unsupported media type, such as `.exe` for an image upload.\n\n### 416 Range Not Satisfiable\n- **Description**: Requested range not available.\n- **Example**: Requesting a range beyond file length.\n\n### 417 Expectation Failed\n- **Description**: Expectation in headers cannot be met.\n- **Example**: Server fails to meet `Expect: 100-continue` header.\n\n### 418 I'm a Teapot (RFC 2324)\n- **Description**: April Fools' joke status code.\n- **Example**: For fun, returned by a teapot API as a joke.\n\n### 421 Misdirected Request\n- **Description**: Request was directed to a server that cannot respond.\n- **Example**: Server configuration issue causing requests to be misdirected.\n\n### 422 Unprocessable Entity (WebDAV)\n- **Description**: Request is well-formed but has semantic errors.\n- **Example**: Valid JSON payload with invalid data.\n\n### 423 Locked (WebDAV)\n- **Description**: Resource is locked.\n- **Example**: Editing a locked document returns `423 Locked`.\n\n### 424 Failed Dependency (WebDAV)\n- **Description**: Failed due to dependency on another action.\n- **Example**: Chained requests where one fails, causing others to fail.\n\n### 425 Too Early\n- **Description**: Indicates request might be replayed.\n- **Example**: When using `Early Data` in HTTP/2 connections.\n\n### 426 Upgrade Required\n- **Description**: Client should upgrade to a different protocol.\n- **Example**: Server requires client to upgrade to HTTP/2.\n\n### 428 Precondition Required\n- **Description**: Requires conditions to prevent conflicts.\n- **Example**: PUT request that includes conditional headers.\n\n### 429 Too Many Requests\n- **Description**: Rate limit exceeded.\n- **Example**: Frequent API calls triggering rate limits.\n\n### 431 Request Header Fields Too Large\n- **Description**: Headers too large for the server.\n- **Example**: Long headers like cookies exceeding limits.\n\n### 451 Unavailable For Legal\n\n Reasons\n- **Description**: Resource restricted for legal reasons.\n- **Example**: Content blocked due to a court order.\n\n---\n\n## 5. Server Error Responses (500–599)\n\n### 500 Internal Server Error\n- **Description**: General server error.\n- **Example**: Server fails unexpectedly due to a misconfiguration.\n\n### 501 Not Implemented\n- **Description**: Request method not supported.\n- **Example**: Server doesn’t support PATCH requests.\n\n### 502 Bad Gateway\n- **Description**: Server received invalid response from upstream.\n- **Example**: Proxy server cannot reach backend server.\n\n### 503 Service Unavailable\n- **Description**: Server is overloaded or under maintenance.\n- **Example**: Site under maintenance returns `503`.\n\n### 504 Gateway Timeout\n- **Description**: Gateway timed out waiting for a response.\n- **Example**: Proxy fails due to slow backend.\n\n### 505 HTTP Version Not Supported\n- **Description**: HTTP version is not supported by the server.\n- **Example**: Server rejects requests using outdated HTTP versions.\n\n### 506 Variant Also Negotiates\n- **Description**: Circular content negotiation detected.\n- **Example**: Negotiation logic loop.\n\n### 507 Insufficient Storage (WebDAV)\n- **Description**: Not enough storage for request.\n- **Example**: Server unable to upload file due to storage limits.\n\n### 508 Loop Detected (WebDAV)\n- **Description**: Infinite loop detected during processing.\n- **Example**: Server detects recursion in resource.\n\n### 510 Not Extended\n- **Description**: Further extensions required.\n- **Example**: Client needs to extend request with additional requirements.\n\n### 511 Network Authentication Required\n- **Description**: Client must authenticate to access the network.\n- **Example**: Hotel Wi-Fi redirecting to login page.\n\n---\n\nEach status code is essential for efficient HTTP communication. By understanding these codes, developers can better handle responses and errors, enhancing application robustness and reliability.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnomadicmehul%2Fhttp-status-codes","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnomadicmehul%2Fhttp-status-codes","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnomadicmehul%2Fhttp-status-codes/lists"}