HTTP 상태 코드 참조

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

The server is switching protocols as requested by the client in the Upgrade header, for example to WebSocket.

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

Returns some response headers before the final response so the client can start preloading resources.

The request succeeded. The meaning of success depends on the HTTP method used.

The request succeeded and a new resource was created, usually in response to POST or PUT.

The request was accepted for processing, but the processing has not completed and may still fail.

The returned metadata is from a local or third-party copy rather than the origin server.

The request succeeded but there is no content to send in the response body.

The request succeeded and the client should reset the document view that sent the request.

The server is delivering only part of the resource in response to a Range header, used for resumable downloads.

Conveys information about multiple resources where several status codes apply. Used by WebDAV.

The members of a WebDAV binding have already been enumerated and are not being included again.

The server fulfilled a GET request and the response represents the result of instance manipulations applied.

The request has more than one possible response and the client should choose one of them.

The resource has permanently moved to a new URL given in the Location header. Search engines update their links.

The resource is temporarily at a different URL. The client should keep using the original URL for future requests.

The response is at another URL that should be retrieved with a GET request. Common after a form POST.

The cached copy is still valid, so the server sends no body. Used with conditional requests to save bandwidth.

The resource is temporarily at another URL and the client must reuse the same HTTP method and body.

The resource has permanently moved and the client must reuse the same HTTP method and body.

The server cannot process the request because of a client error such as malformed syntax or invalid framing.

Authentication is required and has failed or not been provided. The response includes a WWW-Authenticate header.

Reserved for future use. Occasionally used by APIs to signal that a paid plan or quota is required.

The server understood the request but refuses to authorize it. Authenticating will not help.

The server cannot find the requested resource. The URL may be wrong or the resource may have been removed.

The request method is known but not supported by the target resource, for example POST to a read-only endpoint.

The resource cannot produce a response matching the Accept headers sent by the client.

The client must first authenticate with a proxy before the request can proceed.

The server timed out waiting for the request. The client may repeat the request later.

The request conflicts with the current state of the resource, such as an edit that clashes with another change.

The resource is permanently gone with no forwarding address. More specific and final than 404.

The server refuses the request because it lacks a defined Content-Length header.

A precondition in the request headers, such as If-Match, evaluated to false on the server.

The request body is larger than the server is willing or able to process. Formerly Payload Too Large.

The requested URI is longer than the server is willing to interpret, often from too many query parameters.

The request body is in a format the resource does not support, such as an unexpected Content-Type.

The Range header requests a portion the server cannot supply, for example beyond the end of the file.

The expectation in the Expect request header could not be met by the server.

An April Fools joke code from 1998 that returns when a teapot is asked to brew coffee. Sometimes used as an easter egg.

The request was sent to a server that cannot produce a response for the combination of scheme and authority.

The request is well formed but has semantic errors that prevent processing, common in API validation failures.

The resource being accessed is locked. Used by WebDAV.

The request failed because it depended on another request that failed. Used by WebDAV.

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

The client should switch to a different protocol given in the Upgrade header, such as a newer TLS version.

The origin server requires the request to be conditional to prevent lost-update conflicts.

The client has sent too many requests in a given time. Rate limiting responses often include a Retry-After header.

The server refuses the request because the header fields are too large, individually or in total.

The resource is unavailable because of a legal demand, such as a government censorship order.

A generic error meaning the server hit an unexpected condition and cannot give a more specific message.

The server does not support the functionality required to fulfil the request, such as an unknown method.

A server acting as a gateway or proxy received an invalid response from an upstream server.

The server is temporarily unable to handle the request, usually from overload or maintenance. Retry later.

A gateway or proxy did not get a timely response from the upstream server it needed to complete the request.

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

A content negotiation configuration error caused the chosen variant to itself engage in negotiation.

The server cannot store the representation needed to complete the request. Used by WebDAV.

The server detected an infinite loop while processing the request. Used by WebDAV.

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

The client must authenticate to gain network access, typically shown by a captive portal on public Wi-Fi.