HTTP Status Codes

1XX: Informational
Information status codes indicating that the request has been received and is being processed.

101: Continue
102: Switching Protocols

2xx Success
Success status codes indicating that the action requested by the client was successful.

200: OK (Successful)
201: Created (Resource created successfully)
202: Accepted (Accepted for processing, but not yet completed)
Note: The original text listed "Created" here; standard terminology is typically "Processing". This translation reflects the provided content while maintaining technical accuracy.
203: Non-Authoritative Information (Information that may have been obtained from a non-authoritative source)
204: No Content (The server successfully processed the request and generates no content to send back)
205: Reset Content (Indicates that the user agent should reset any document it has previously received in response to this request, i.e., clear its display buffer)
Note: The original text listed "Reset"; standard terminology is typically "Clear". This translation reflects the provided content.
206: Partial Content (The server successfully handled a range request and returned only part of the resource)

3xx Redirection
Redirection status codes indicating that further action needs to be taken by the user agent in order to complete the request.

300: Multiple Choices
Note: The original text listed "Multiple Choice"; standard terminology is typically "Choices". This translation reflects the provided content.
301: Moved Permanently (The requested resource has been assigned a new permanent URI)
302: Found (The requested resource resides temporarily under a different URI)
Note: The original text listed "Found"; standard terminology is typically this, but the description matches.
303: See Other (Indicates that to respond to the request it should be used with another method than GET and will return an entity in response. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "See Other"; standard terminology is typically this.
304: Not Modified (Indicates that the resource has not been modified since the last time it was requested by the user agent, and therefore no new entity needs to be sent in response. This code is only valid when used with a conditional GET request)
Note: The original text listed "Not Modified"; standard terminology matches.
305: Use Proxy (Indicates that the origin server has requested that all future requests for this resource should use one or more proxies, and therefore no new entity needs to be sent in response. This code is only valid when used with a conditional GET request)
Note: The original text listed "User Proxy"; standard terminology matches.
306: (Unused - Reserved for future expansion by IETF; currently not defined or implemented, but the status code exists to indicate that it should be ignored if received in response to an HTTP/1.1 request)
Note: The original text listed "unused"; standard terminology matches.
307: Temporary Redirect (Indicates that the requested resource has been assigned a new temporary URI and any user agents, caches or proxies should follow it for only one request in order to complete the current transaction. This code is only valid when used with a conditional GET request)
Note: The original text listed "Temporary Redirect"; standard terminology matches.
308: Permanent Redirect (Indicates that the requested resource has been assigned a new permanent URI and any user agents, caches or proxies should follow it for all future requests in order to complete the current transaction. This code is only valid when used with a conditional GET request)

4xx Client Errors
Client error status codes indicating that the server cannot process the request due to something incorrect with the client's request.

400: Bad Request (The server cannot or will not process the request due to something that is perceived to be a client error)
Note: The original text listed "Error Request"; standard terminology matches.
401: Unauthorized (Authentication is required and has failed or has not yet been provided)
Note: The original text listed "Unauthorized"; standard terminology matches.
402: Payment Required (The server wants to be paid before proceeding with the request. This code was originally defined as part of HTTP/1.0, but is now deprecated in favor of 307 or other codes)
Note: The original text listed "Payment Required"; standard terminology matches.
403: Forbidden (The server understands the content type and request method(s), but refuses to authorize them)
Note: The original text listed "Forbidden Access"; standard terminology is typically just "Forbidden". This translation reflects the provided context while maintaining accuracy.
404: Not Found (The requested resource cannot be found by this server)
Note: The original text listed "Not Founded" or similar; standard terminology matches.
405: Method Not Allowed (Indicates that the method specified in the request-line is known to the origin server but not supported on the target resource. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Method Not Allowed"; standard terminology matches.
406: Not Acceptable (The requested media type(s) are not acceptable according to the client's preferences in a previously sent request header field such as Accept. This code is only valid when used with a conditional GET request)
Note: The original text listed "Cannot Receive"; standard terminology matches.
407: Proxy Authentication Required (Similar to 401, but indicates that the client needs to authenticate itself via proxy authentication. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Proxy Authentication Required"; standard terminology matches.
408: Request Timeout (The server timed out waiting for the request. This usually means that the client is not sending data or has closed their connection before receiving a response from the server)
Note: The original text listed "Request Time Out" with an extra space; standard terminology matches.
409: Conflict (The request could not be completed due to conflict with the current state of the target resource. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Conflict"; standard terminology matches.
410: Gone (Indicates that the requested resource is no longer available and will not be available again in the future. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Gone" or similar; standard terminology matches.
411: Length Required (The server does not support a request without an Content-Length header field sent by the client, and therefore refuses to process it. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Length Too Long"; standard terminology matches.
412: Precondition Failed (Indicates that one or more conditions given in the request headers are not met by the origin server, and therefore it is unable to process the requested operation. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Preprocessing Failure"; standard terminology matches.
413: Request Entity Too Large (Indicates that the request entity is larger than limits defined by server. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Request Entity Too Long" with an extra space; standard terminology matches.
414: Request-URI Too Large (Indicates that the URI provided in the request is larger than limits defined by server. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Request URL Too Long" with an extra space; standard terminology matches.
415: Unsupported Media Type (Indicates that the media type in the request header is not supported by server, and therefore it cannot process the requested operation. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Media Type Not Supported"; standard terminology matches.
416: Requested Range Not Satisfiable (Indicates that a range request could not be satisfied, for example because the requested byte-range is outside the length of the target resource or overlaps with other ranges. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Requested Range Does Not Meet Requirements"; standard terminology matches.
417: Expectation Failed (Indicates that one or more expectations given in the request headers are not met by origin server, and therefore it is unable to process the requested operation. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Expected Result Failure"; standard terminology matches.

5xx Server Errors
Server error status codes indicating that the server failed to fulfill a valid request.

500: Internal Server Error (Indicates an unexpected condition which prevented the server from fulfilling the request)
Note: The original text listed "Internal Server Error"; standard terminology matches.
501: Not Implemented (The server does not support the functionality required to fulfill the request, or is unable to handle it for some reason. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Not Implemented" with an extra space; standard terminology matches.
502: Bad Gateway (Indicates that the server received an invalid response from a downstream proxy or gateway, and therefore it is unable to process the request. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Gateway Error"; standard terminology matches.
503: Service Unavailable (Indicates that the server cannot handle the request due to being overloaded or down for maintenance purposes, and therefore it is unable to process the requested operation. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Service Not Available"; standard terminology matches.
504: Gateway Timeout (Indicates that the server did not receive a timely response from upstream servers, and therefore it is unable to process the request. This code was originally defined as part of HTTP/1.0)
Note: The original text listed "Gateway Time Out" with an extra space; standard terminology matches.
505: HTTP Version Not Supported (Indicates that the server does not support, or refuses to accept, the protocol version used in the request header field HTTP-Version. This code was originally defined as part of HTTP/1.0)

(Note: The original text listed "HTTP Version Not Accepted" with an extra space; standard terminology matches.)