HTTPステータスコード

Continue

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

Switching Protocols

The server is switching protocols as requested by the client.

Processing

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

Early Hints

Used to preload resources while the server prepares a final response.

OK

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

Created

The request succeeded and a new resource was created as a result.

Accepted

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

Non-Authoritative Information

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

No Content

The server successfully processed the request and is not returning any content.

Reset Content

The server processed the request and asks the client to reset the document view.

Partial Content

The server is delivering only part of the resource due to a range request.

Multi-Status

Conveys information about multiple resources, for WebDAV responses.

Already Reported

Used inside a DAV binding to avoid enumerating the members of multiple bindings.

IM Used

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

Multiple Choices

The request has more than one possible response. The user should choose one of them.

Moved Permanently

The URL of the requested resource has been changed permanently.

Found

The URI of requested resource has been changed temporarily.

See Other

The server sends this response to direct the client to get the requested resource at another URI with a GET request.

Not Modified

This is used for caching purposes. The response has not been modified, so the client can continue to use the same cached version.

Temporary Redirect

The server sends this response to direct the client to get the requested resource at another URI with the same method.

Permanent Redirect

The resource is now permanently located at another URI. Same as 301 but the HTTP method must not change.

Bad Request

The server cannot process the request due to malformed syntax or invalid parameters.

Unauthorized

Authentication is required and has failed or has not yet been provided.

Payment Required

Reserved for future use; sometimes used for digital payment systems.

Forbidden

The client does not have access rights to the content; the server refuses to give the requested resource.

Not Found

The server cannot find the requested resource. The URL is not recognized.

Method Not Allowed

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

Not Acceptable

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

Proxy Authentication Required

Authentication is needed to be done by a proxy.

Request Timeout

The server did not receive a complete request message within the time it was prepared to wait.

Conflict

The request conflicts with the current state of the server.

Gone

The requested content has been permanently deleted from the server, with no forwarding address.

Length Required

The server requires the Content-Length header field.

Precondition Failed

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

Content Too Large

The request entity is larger than limits defined by the server.

URI Too Long

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

Unsupported Media Type

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

Range Not Satisfiable

The range specified by the Range header field cannot be fulfilled.

Expectation Failed

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

I'm a Teapot

The server refuses to brew coffee because it is a teapot. (RFC 2324 April Fools' joke)

Unprocessable Content

The request was well-formed but unable to be followed due to semantic errors.

Locked

The resource that is being accessed is locked (WebDAV).

Failed Dependency

The request failed because it depended on another request that failed (WebDAV).

Too Early

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

Upgrade Required

The client should switch to a different protocol such as TLS/1.3.

Precondition Required

The origin server requires the request to be conditional.

Too Many Requests

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

Request Header Fields Too Large

The server is unwilling to process the request because its header fields are too large.

Unavailable For Legal Reasons

The user requested a resource that cannot legally be provided.

Internal Server Error

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

Not Implemented

The request method is not supported by the server and cannot be handled.

Bad Gateway

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

Service Unavailable

The server is not ready to handle the request. Common causes: maintenance or overload.

Gateway Timeout

The server, while acting as a gateway, did not get a response in time from the upstream server.

HTTP Version Not Supported

The HTTP version used in the request is not supported by the server.

Variant Also Negotiates

The server has an internal configuration error with transparent content negotiation.

Insufficient Storage

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

Loop Detected

The server detected an infinite loop while processing the request (WebDAV).

Not Extended

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

Network Authentication Required

The client needs to authenticate to gain network access.