HTTPステータスコード開発
全HTTPステータスコードのクイックリファレンス
⌘K
1xx
Informational
4 個
| コード | 名前 | 説明 |
|---|---|---|
| Continue | The server has received the request headers and the client should proceed to send the request body. | |
| Switching Protocols | The requester has asked the server to switch protocols and the server has agreed to do so. | |
| Processing | The server has received and is processing the request, but no response is available yet. | |
| Early Hints | Used to return some response headers before the final HTTP message. |
2xx
Success
10 個
| コード | 名前 | 説明 |
|---|---|---|
| OK | The request has succeeded. The meaning of success depends on the HTTP method. | |
| Created | The request has been fulfilled and a new resource has been created. | |
| Accepted | The request has been accepted for processing, but processing has not been completed. | |
| Non-Authoritative Information | The server successfully processed the request but is returning information from another source. | |
| No Content | The server successfully processed the request and is not returning any content. | |
| Reset Content | The server successfully processed the request and asks the requester to reset its document view. | |
| Partial Content | The server is delivering only part of the resource due to a range header sent by the client. | |
| Multi-Status | The response body contains multiple separate response codes for batch operations. | |
| Already Reported | The members of a DAV binding have already been enumerated in a preceding part of the response. | |
| IM Used | The server has fulfilled a request and the response is the result of instance manipulations on the current instance. |
3xx
Redirection
7 個
| コード | 名前 | 説明 |
|---|---|---|
| Multiple Choices | Indicates multiple options for the resource from which the client may choose. | |
| Moved Permanently | This and all future requests should be directed to the given URI. | |
| Found | The resource is temporarily located at a different URI. | |
| See Other | The response to the request can be found under another URI using the GET method. | |
| Not Modified | The resource has not been modified since the version specified by the request headers. | |
| Temporary Redirect | The request should be repeated at another URI, but future requests should still use the original URI. | |
| Permanent Redirect | The request and all future requests should be repeated using another URI, preserving the HTTP method. |
4xx
Client Error
40 個
| コード | 名前 | 説明 |
|---|---|---|
| Bad Request | The server cannot process the request due to a client error, such as malformed syntax. | |
| Unauthorized | Authentication is required and has failed or has not been provided. | |
| Payment Required | Reserved for future use, originally intended for digital payment systems. | |
| Forbidden | The server understood the request but refuses to authorize it. | |
| Not Found | The requested resource could not be found but may be available in the future. | |
| Method Not Allowed | The request method is not supported for the requested resource. | |
| Not Acceptable | The server cannot produce a response matching the acceptable values in the request headers. | |
| Proxy Authentication Required | The client must first authenticate itself with the proxy. | |
| Request Timeout | The server timed out waiting for the request. | |
| Conflict | The request could not be processed because of a conflict with the current state of the resource. | |
| Gone | The resource requested was previously in use but is no longer available and will not be available again. | |
| Length Required | The server refuses to accept the request without a defined Content-Length header. | |
| Precondition Failed | The server does not meet one of the preconditions specified in the request headers. | |
| Content Too Large | The request body is larger than the server is willing or able to process. | |
| URI Too Long | The URI provided was too long for the server to process. | |
| Unsupported Media Type | The request entity has a media type which the server or resource does not support. | |
| Range Not Satisfiable | The client has asked for a portion of the file, but the server cannot supply that portion. | |
| Expectation Failed | The server cannot meet the requirements of the Expect request-header field. | |
| I'm a Teapot | Defined in RFC 2324 as an April Fools' joke; a teapot refuses to brew coffee. | |
| Enhance Your Calm | Twitter/XRate limiting response. Non-standard; superseded by 429 Too Many Requests. | |
| Misdirected Request | The request was directed at a server that is not able to produce a response. | |
| Unprocessable Content | The request was well-formed but could not be followed due to semantic errors. | |
| Locked | The resource that is being accessed is locked. | |
| Failed Dependency | The request failed because it depended on another request that failed. | |
| 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 to prevent conflicts. | |
| 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 the header fields are too large. | |
| Login Timeout | IISThe client's session has expired and must log in again. | |
| No Response | nginxCloses the connection without sending any response, typically used to deny malicious requests. | |
| Retry With | IISThe server requires the client to resend the request with more information. | |
| Unavailable For Legal Reasons | The server is denying access to the resource as a consequence of a legal demand. | |
| Client Closed Connection | AWSThe client closed the connection before the load balancer could send the request to the target. | |
| Too Many IP Addresses | AWSThe X-Forwarded-For header contains more than 30 IP addresses. | |
| Request Header Too Large | nginxThe request headers exceed the server's configured limit. | |
| SSL Certificate Error | nginxAn error occurred while verifying the client SSL certificate. | |
| SSL Certificate Required | nginxThe client did not provide a required SSL certificate. | |
| HTTP Request Sent to HTTPS Port | nginxA plain HTTP request was sent to an HTTPS port. | |
| Client Closed Request | nginxThe client closed the connection before the server could send a response. |
5xx
Server Error
21 個
| コード | 名前 | 説明 |
|---|---|---|
| Internal Server Error | A generic error message when the server encounters an unexpected condition. | |
| Not Implemented | The server does not recognize the request method or lacks the ability to fulfill it. | |
| Bad Gateway | The server, acting as a gateway or proxy, received an invalid response from the upstream server. | |
| Service Unavailable | The server is temporarily unable to handle the request, due to overload or scheduled maintenance. | |
| Gateway Timeout | The server, acting as a gateway or proxy, did not receive a timely response from the upstream server. | |
| HTTP Version Not Supported | The server does not support the HTTP version used in the request. | |
| Variant Also Negotiates | Transparent content negotiation for the request results in a circular reference. | |
| Insufficient Storage | The server is unable to store the representation needed to complete the request. | |
| Loop Detected | The server detected an infinite loop while processing the request. | |
| Not Extended | Further extensions to the request are required for the server to fulfill it. | |
| Network Authentication Required | The client needs to authenticate to gain network access (e.g., captive portal). | |
| Web Server Returns an Unknown Error | CloudflareThe origin server returned an empty, unknown, or unexpected response. | |
| Web Server Is Down | CloudflareThe origin server refused the connection. | |
| Connection Timed Out | CloudflareThe TCP handshake with the origin server timed out. | |
| Origin Is Unreachable | CloudflareCannot reach the origin server, possibly due to DNS resolution failure. | |
| A Timeout Occurred | CloudflareA TCP connection was established but the origin server did not reply in time. | |
| SSL Handshake Failed | CloudflareThe SSL handshake with the origin server failed. | |
| Invalid SSL Certificate | CloudflareCould not validate the SSL certificate on the origin server. | |
| Railgun Error | CloudflareThe Railgun connection to the origin server was interrupted (deprecated feature). | |
| Origin DNS Error | CloudflareCannot resolve the origin server's DNS, usually accompanied by a 1xxx error. | |
| Unauthorized | AWSThe identity provider returned an error code during authentication. |