HTTP Status Code Query

Quickly look up HTTP status code meanings, understand network request responses, server errors, and client errors.

Green Tool
{ "columns": [ { "id": "code", "header": "Status Code", "accessorKey": "code" }, { "id": "title", "header": "Description", "accessorKey": "title" }, { "id": "description", "header": "Description", "accessorKey": "description" }, { "id": "category", "header": "Category", "accessorKey": "category" } ], "data": [ { "code": "100", "title": "Continue", "description": "The requester should continue with the request. The server returns this code to indicate that it has received the first part of the request and is waiting for the rest\nThe server has received the request headers and the client should proceed to send the request body.", "category": "1xx Status: Informational Response" }, { "code": "101", "title": "Switching Protocols", "description": "The requester has asked the server to switch protocols, and the server has confirmed and is ready to switch\nThe requester has asked the server to switch protocols and the server has agreed to do so.", "category": "1xx Status: Informational Response" }, { "code": "200", "title": "Success", "description": "The server has successfully processed the request. Usually, this means the server has provided the requested web page\nStandard response for successful HTTP requests.", "category": "2xx Status: Successful Response" }, { "code": "201", "title": "Created", "description": "The request was successful, and the server created a new resource\nThe request has been fulfilled, resulting in the creation of a new resource.", "category": "2xx Status: Successful Response" }, { "code": "202", "title": "Accepted", "description": "The server has accepted the request but has not yet processed it\nThe request has been accepted for processing, but the processing has not been completed.", "category": "2xx Status: Successful Response" }, { "code": "203", "title": "Non-Authoritative Information", "description": "The server has successfully processed the request, but the returned information may be from another source\nThe server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response.", "category": "2xx Status: Successful Response" }, { "code": "204", "title": "No Content", "description": "The server successfully processed the request but did not return any content\nThe server successfully processed the request and is not returning any content.", "category": "2xx Status: Successful Response" }, { "code": "205", "title": "Reset Content", "description": "The server successfully processed the request but did not return any content. This response asks the browser to reset the content it displays\nThe server successfully processed the request, but is not returning any content. This response requires that the requester reset the document view.", "category": "2xx Status: Successful Response" }, { "code": "206", "title": "Partial Content", "description": "The server successfully returned part of the resource because the client sent a range header\nThe server is delivering only part of the resource due to a range header sent by the client.", "category": "2xx Status: Successful Response" }, { "code": "300", "title": "Multiple Choices", "description": "The server can perform multiple operations for different requests. The server can perform the corresponding operation based on the requester's choice, or provide a list of operations for the requester to choose from\nIndicates that multiple options for the resource from which the client may choose.", "category": "3xx Status: Redirection" }, { "code": "301", "title": "Moved Permanently", "description": "The requested web page has been permanently moved to a new location. For GET or HEAD requests, when the server returns this response, it will automatically redirect the requester to the new location\nIndicates the resource had been moved to another location permanently. This and all future requests should be directed to the given URI.", "category": "3xx Status: Redirection" }, { "code": "302", "title": "Found (Moved Temporarily)", "description": "Tells the client to get the required resource from another URL (this status has been superseded by 303 and 307 statuses)\nTells the client to look at (browse to) another URL (302 code has been superseded by 303 and 307).", "category": "3xx Status: Redirection" }, { "code": "303", "title": "See Other", "description": "The server returns this code when the requester should use a separate GET request to a different location to retrieve the resource\nThe response to the request can be found under another URI using the GET method.", "category": "3xx Status: Redirection" }, { "code": "304", "title": "Not Modified", "description": "The web page has not been modified since the last request. When the server returns this response, it will not return the content of the web page\nIndicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.", "category": "3xx Status: Redirection" }, { "code": "305", "title": "Use Proxy", "description": "The requester can only access the requested resource using a proxy. The resource address will be included in the response (for security reasons, many clients will not comply with this response status)\nThe requested resource is available only through a proxy, the address for which is provided in the response.", "category": "3xx Status: Redirection" }, { "code": "306", "title": "Switch Proxy", "description": "Subsequent requests should use the specified proxy (this status code is no longer used in the latest HTTP specification)\nNo longer used. Subsequent requests should use the specified proxy.", "category": "3xx Status: Redirection" }, { "code": "307", "title": "Temporary Redirect", "description": "The requester should re-initiate a request with another URL, but subsequent requests should still use the original URL\nThe request should be repeated with another URI; however, future requests should still use the original URI.", "category": "3xx Status: Redirection" }, { "code": "308", "title": "Permanent Redirect", "description": "The current request and all subsequent requests should be made to another URL\nThe request and all future requests should be repeated using another URI.", "category": "3xx Status: Redirection" }, { "code": "400", "title": "Bad Request", "description": "The server does not understand the syntax of the client's request, such as incorrect request syntax, excessively large request body, or deceptive request paths\nThe server cannot or will not process the request due to an apparent client error.", "category": "4xx Status: Client Error" }, { "code": "401", "title": "Unauthorized", "description": "Access to the resource requires authentication, but no authorization was provided or incorrect authorization was provided during the request. For web pages that require login, the server may return this response\nThe resource which authentication is required and not yet been provided (or failed).", "category": "4xx Status: Client Error" }, { "code": "402", "title": "Payment Required", "description": "Reserved for future use. Usually used in scenarios requiring payment, such as digital currency or online payment. An example is: Google Developer API uses 402 status to indicate that the daily request limit has been exceeded\nReserved for future use. Might be used as part of some form of digital cash or micropayment scheme, but that has not yet happened.", "category": "4xx Status: Client Error" }, { "code": "403", "title": "Forbidden", "description": "The server has received the request but refuses to provide the service. This status usually occurs because the requester does not have sufficient permissions to access the requested resource\nThe request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action.", "category": "4xx Status: Client Error" }, { "code": "404", "title": "Not Found", "description": "The server cannot find the requested web page or resource\nThe requested resource could not be found but may be available in the future.", "category": "4xx Status: Client Error" }, { "code": "405", "title": "Method Not Allowed", "description": "The server does not support the current request method. For example: some resources only support GET and POST requests, if a HEAD request is initiated, the server will return this status\nA request method is not supported for the requested resource.", "category": "4xx Status: Client Error" }, { "code": "406", "title": "Not Acceptable", "description": "The server cannot respond to the requested web page using the content characteristics of the request, i.e., it does not support the content corresponding to the Accept field in the request header\nThe requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.", "category": "4xx Status: Client Error" }, { "code": "407", "title": "Proxy Authentication Required", "description": "This status code is similar to 401 (Unauthorized), but specifies that the requester should authorize the use of a proxy\nThe client must first authenticate itself with the proxy.", "category": "4xx Status: Client Error" }, { "code": "408", "title": "Request Timeout", "description": "A timeout occurred while the server was waiting for the request\nThe server timed out waiting for the request.", "category": "4xx Status: Client Error" }, { "code": "409", "title": "Conflict", "description": "A conflict occurred while the server was completing the request. The server must include information about the conflict in the response\nIndicates that the request could not be processed because of conflict in the current state of the resource.", "category": "4xx Status: Client Error" }, { "code": "410", "title": "Gone", "description": "If the requested resource has been permanently deleted, the server will return this response\nIndicates that the resource requested is no longer available and will not be available again.", "category": "4xx Status: Client Error" }, { "code": "411", "title": "Length Required", "description": "The server cannot process requests that do not contain a Content-Length header field\nThe request did not specify the length of its content, which is required by the requested resource.", "category": "4xx Status: Client Error" }, { "code": "412", "title": "Precondition Failed", "description": "The server did not meet one of the preconditions set by the requester in the request\nThe server does not meet one of the preconditions that the requester put on the request header fields.", "category": "4xx Status: Client Error" }, { "code": "413", "title": "Payload Too Large", "description": "The server cannot process the request because the request entity is too large, exceeding the server's processing capacity\nThe request is larger than the server is willing or able to process. Previously called \"Request Entity Too Large\".", "category": "4xx Status: Client Error" }, { "code": "414", "title": "URI Too Long", "description": "The requested URI (usually a URL) is too long for the server to process\nThe URI provided was too long for the server to process. Called \"Request-URI Too Long\" previously.", "category": "4xx Status: Client Error" }, { "code": "415", "title": "Unsupported Media Type", "description": "The server does not support the content format (Content-Type) of the request\nThe request entity has a media type which the server or resource does not support.", "category": "4xx Status: Client Error" }, { "code": "416", "title": "Range Not Satisfiable", "description": "When the client requests a part of the server resource, but the server cannot provide that part, this status code will be returned\nThe client has asked for a portion of the file (byte serving), but the server cannot supply that portion.", "category": "4xx Status: Client Error" }, { "code": "417", "title": "Expectation Failed", "description": "This status code is returned when the server cannot meet the requirements of the \"Expect\" request header\nThe server cannot meet the requirements of the Expect request-header field.", "category": "4xx Status: Client Error" }, { "code": "421", "title": "Misdirected Request", "description": "This status is returned when the request is directed to a server that cannot produce a response\nThe request was directed at a server that is not able to produce a response.", "category": "4xx Status: Client Error" }, { "code": "422", "title": "Unprocessable Entity", "description": "The request format is correct, but due to semantic errors, the request cannot be responded to\nThe request was well-formed but was unable to be followed due to semantic errors.", "category": "4xx Status: Client Error" }, { "code": "423", "title": "Locked", "description": "The resource being accessed is locked\nThe resource that is being accessed is locked.", "category": "4xx Status: Client Error" }, { "code": "424", "title": "Failed Dependency", "description": "The current request failed because a previous request (i.e., a dependent request) failed\nThe request failed because it depended on another request and that request failed.", "category": "4xx Status: Client Error" }, { "code": "500", "title": "Internal Server Error", "description": "An internal server error occurred and the request could not be completed\nA generic error message, given when an unexpected condition was encountered and no more specific message is suitable.", "category": "5xx Status: Server Error" }, { "code": "501", "title": "Not Implemented", "description": "The server is not yet capable of fulfilling the request: either the request method is not recognized; or it lacks the ability to fulfill the request\nThe server either does not recognize the request method, or it lacks the ability to fulfil the request.", "category": "5xx Status: Server Error" }, { "code": "502", "title": "Bad Gateway", "description": "The server, acting as a gateway or proxy, received an invalid response from an upstream server\nThe server was acting as a gateway or proxy and received an invalid response from the upstream server.", "category": "5xx Status: Server Error" }, { "code": "503", "title": "Service Unavailable", "description": "The server is currently unavailable (due to overload or maintenance). This is usually a temporary state\nThe server can't handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.", "category": "5xx Status: Server Error" }, { "code": "504", "title": "Gateway Timeout", "description": "The server, acting as a gateway or proxy, did not receive a timely response from an upstream server\nThe server was acting as a gateway or proxy and did not receive a timely response from the upstream server.", "category": "5xx Status: Server Error" }, { "code": "505", "title": "HTTP Version Not Supported", "description": "The server does not support the HTTP protocol version used in the request\nThe server does not support the HTTP protocol version used in the request.", "category": "5xx Status: Server Error" } ] }

Related Tools

Tool Introduction

"HTTP Status Code Query" is a convenient online tool designed to help users quickly look up and understand the detailed meanings of various HTTP status codes. This tool systematically categorizes HTTP status codes into five major series: 1xx (Informational responses), 2xx (Successful responses), 3xx (Redirection), 4xx (Client errors), and 5xx (Server errors), clearly displaying each status code's Chinese name, Chinese description, English description, and related protocol version or RFC definition information. Whether you are a developer, website administrator, or network enthusiast, this tool can help you efficiently diagnose network problems and enhance your understanding of the HTTP protocol.

How to Use

  1. Browse Categories: The tool page logically groups HTTP status codes by numerical range (1xx, 2xx, 3xx, 4xx, 5xx). Users can directly navigate to the corresponding category area based on the status code range they need to focus on.
  2. View Detailed Information: Under each status code entry, you can view the status code's numerical code, its corresponding Chinese name (e.g., "200 OK"), detailed Chinese description, and official English description.
  3. Special Notes: Some status codes also come with additional explanatory tags, such as "Supported since HTTP/1.1", "This status code is defined by RFC 7233", or "This status code is deprecated". This information helps users gain a more comprehensive understanding of the status code's background and applicability.

Input parameter format and requirements: This tool is purely a query reference tool and does not require users to input any parameters. All information is pre-organized and displayed.

Output result format: The tool displays HTTP status codes and their detailed information in a clear, structured list format. The detailed content for each status code includes: status code number, Chinese name, Chinese description, English description, and optional specification source or version support tags.

 

Frequently Asked Questions

  • Q: Does this tool support real-time querying of a specific HTTP status code?
  • A: This tool is a comprehensive reference list. You can quickly locate and query detailed information for any HTTP status code by browsing or using your browser's built-in search function (Ctrl+F / Cmd+F).
  • Q: What types of information does this tool primarily provide?
  • A: This tool primarily provides the numerical code of HTTP status codes, Chinese names, detailed Chinese descriptions, official English descriptions, and related protocol version support information (e.g., HTTP/1.1 support, RFC definitions, etc.).
  • Q: What are the classification standards for HTTP status codes?
  • A: HTTP status codes are typically divided into five main categories: 1xx (Informational responses), 2xx (Successful responses), 3xx (Redirection), 4xx (Client errors), and 5xx (Server errors). This tool also strictly adheres to this standard for classification display.

Notes

  • This tool is for HTTP status code lookup and reference only and does not provide actual network request or testing functions.
  • Some status codes (such as 306 Switch Proxy) have been deprecated by HTTP specifications, but may still exist in older systems. Please pay attention to their compatibility and deprecated status when using them.
  • When using tags such as "Supported since HTTP/1.1" or "This status code is defined by RFC XXXX" mentioned in the tool, please pay attention to the corresponding HTTP protocol version and RFC document to ensure an accurate understanding of their applicable scenarios.

Rating

0 / 5

0 ratings

Statistics

Views: 3131

Uses: 3151