Referensi Kode Status HTTP

The server has received the request headers and the client should proceed to send the request body.

The server is switching protocols as requested by the client via the Upgrade header.

The server has received and is processing the request, but no response is available yet.

The server is sending preliminary headers to allow the client to preload resources before the final response.

The request has succeeded. The meaning depends on the HTTP method used.

The request has been fulfilled and a new resource has been created.

The request has been accepted for processing, but the processing has not been completed.

The returned metadata is not exactly the set available from the origin server but is gathered from a local or third-party copy.

The server has fulfilled the request but does not need to return a response body.

The server has fulfilled the request and the user agent should reset the document view.

The server is delivering only part of the resource due to a Range header sent by the client.

Provides status for multiple independent operations in WebDAV.

The members of a DAV binding have already been enumerated in a previous reply to this request.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

The request has more than one possible response. The user agent or user should choose one.

The resource has been permanently moved to a new URL indicated by the Location header.

The resource has been temporarily moved to a different URL.

The response to the request can be found at another URL using a GET method.

The resource has not been modified since the last request, and the client should use its cached version.

The requested resource must be accessed through the proxy specified in the Location header.

Subsequent requests should use the specified proxy.

The resource has been temporarily moved, and the client should use the same HTTP method for the redirect.

The resource has been permanently moved, and the client should use the same HTTP method for the redirect.

The server cannot process the request due to a client error (malformed syntax, invalid request message framing, or deceptive request routing).

The request requires user authentication. The response must include a WWW-Authenticate header.

This response code is reserved for future use. Originally intended for digital payment systems.

The client does not have access rights to the content, and the server is refusing to respond.

The server cannot find the requested resource. In an API, this can also mean the endpoint is valid but the resource itself does not exist.

The request method is known by the server but is not supported by the target resource.

The server cannot produce a response matching the list of acceptable values defined in the request headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

The request conflicts with the current state of the server.

The requested resource is no longer available and will not be available again.

The server refuses to accept the request without a defined Content-Length header.

One or more conditions given in the request header fields evaluated to false.

The request entity is larger than the server is willing or able to process.

The URI provided in the request was too long for the server to process.

The media format of the requested data is not supported by the server.

The range specified in the Range header cannot be satisfied.

The expectation indicated by the Expect request header field cannot be met by the server.

The server refuses to brew coffee because it is, permanently, a teapot.

The request was directed at a server that cannot produce a response for the target resource.

The request body contains well-formed but semantically erroneous content.

The resource that is being accessed is locked.

The request failed because it depended on another operation that failed.

The server is unwilling to risk processing a request that might be replayed.

The client should switch to a different protocol as specified in the Upgrade header.

The server requires the request to be conditional to prevent the lost update problem.

The user has sent too many requests in a given amount of time (rate limiting).

The server refuses to process the request because the header fields are too large.

The resource is unavailable due to legal demands (government censorship, copyright claims).

The server encountered an unexpected condition that prevented it from fulfilling the request.

The server does not support the functionality required to fulfill the request.

The server, while acting as a gateway or proxy, received an invalid response from the upstream server.

The server is currently unable to handle the request due to temporary overload or maintenance.

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.

The server does not support the HTTP protocol version used in the request.

The server has an internal configuration error and the chosen variant resource is configured to engage in transparent content negotiation itself.

The server is unable to store the representation needed to complete the request.

The server detected an infinite loop while processing a request with "Depth: infinity".

Further extensions to the request are required for the server to fulfill it.

The client needs to authenticate to gain network access (e.g., captive portal).