View the HTTP request return status code table details

Status Code	Description
100	Continue The initial request has been accepted, and the customer should continue to send the rest of the request
101	Switching protocols The server converts a client-compliant request to another protocol.
200	OK Indicates that the request is successful and the request information is contained in the response. This is the most frequently received statusCode
201	Created Indicates the request to create a new resource before the response is sent.
202	Accepted Indicates that the request has been accepted for further processing
203	Non-authoritative information Indicates that the returned metadata comes from the cached copy instead of the original server. Therefore, it may be incorrect.
204	NO content Indicates that the request has been processed successfully and the response has been set to NO content
205	Reset content Indicates that the client should reset (or reload) the current resource
206	Partial content Indicates that the response is a partial response of a GET request that contains a byte range.
207	Multi-status
226	Im used
300	Multiple Choices Indicates that the request information has multiple forms of representation. The default operation is to treat this status as redirection and follow the content of the Location header associated with this response
301	moved permanently indicates that the request information has been moved to the URI specified in the location header. When receiving this status, the default operation follows the location header associated with the response. When the original request method is post, the redirected request uses the get method
302	Found Indicates that the request information is located at the URI specified in the location header. When receiving this status, the default operation follows the location header associated with the response. When the original request method is post, the redirected request uses the get method.
303	See other Similar to 301/302, the difference is that if the original request is post, the redirection target document specified by the location header should be extracted through get
304	Not modified The client has a buffered document and sends a conditional request (generally, the IF-modified-since header is provided to indicate that the customer only wants to update the document on a specified date ). The server tells the customer that the previously buffered documents can still be used.
305	Use proxy The document requested by the customer should be extracted from the proxy server specified by the location header
306	Unused Is a recommended extension of the HTTP/1.1 specification that is not fully specified
307	Temporary redirect It is the same as 302 (found. Many browsers mistakenly respond to the 302 response for redirection. Even if the original request is post, it can only be redirected when the POST request actually responds to 303. For this reason, HTTP 1.1 adds 307 to clear the region code in several states: When a 303 response occurs, the browser can follow the redirected get and post requests; if a 307 response occurs, then the browser can only follow the redirection of the GET request
400	Bad request Syntax Error in the request
401	Unauthorized Access is denied. The customer tries to access the password-protected page without authorization. The response contains a WWW-Authenticate header. the browser displays the username/password dialog box accordingly, and then sends a request again after entering the appropriate authorization header. IIS defines many different 401 errors, which indicate more specific error causes. These specific error codes are displayed in the browser but not in the IIS log: 401.1-Logon Failed. 401.2-login failed due to server configuration. 401.3-the ACL is not authorized due to resource restrictions. 401.4-filter authorization failed. 401.5-ISAPI/cgi applicationProgramAuthorization failed. 401.7-the access is rejected by the URL Authorization Policy on the Web server. This error code is dedicated to IIS 6.0.
402	Payment required Retain paymentrequired for future use
403	forbidden the resource is unavailable. The server understands the customer's request, but rejects the request. This is usually caused by permission settings for files or directories on the server. Forbidden access: IIS defines many different 403 errors, which indicate a more specific cause of the error: 403.1-the execution access is forbidden. 403.2-Read access is forbidden. 403.3-write access is forbidden. 403.4-SSL is required. 403.5-SSL 128 is required. 403.6-the IP address is rejected. 403.7-client certificate required. 403.8-site access is denied. 403.9-too many users. 403.10-the configuration is invalid. 403.11-change the password. 403.12-access to the ing table is denied. 403.13-the client certificate is revoked. 403.14-reject the directory list. 403.15-the access permission of the client is exceeded. 403.16-the client certificate is untrusted or invalid. 403.17-the client certificate has expired or has not yet taken effect. 403.18-the requested URL cannot be executed in the current application pool. This error code is dedicated to IIS 6.0. 403.19-CGI cannot be executed for clients in the application pool. This error code is dedicated to IIS 6.0. 403.20-logon to passport failed. This error code is dedicated to IIS 6.0.
404	Not found The resource at the specified location cannot be found. This is also a common response. · 404.0-(none)-No file or directory found. · 404.1-unable to access the web site on the requested port. · 404.2-the Web service extended locking policy blocks this request. · 404.3-the mime ing policy blocks this request.
405	Method not allowed Request methods (get, post, Head, delete, put, Trace, etc.) are not applicable to specified resources and HTTP predicates used to access this page are not allowed (methods are not allowed)
406	Not acceptable The specified resource has been found, but its MIME type is incompatible with the one specified in the accpet header. The client browser does not accept the MIME type of the requested page.
407	Proxy authentication required Requires proxy authentication, similar to 401, indicating that the customer must first be authorized by the Proxy Server
408	Request time-out The customer has not issued any request within the waiting time of the server license. The customer can repeat the same request later
409	Conflict It is usually related to put requests. The request cannot be successful because the request conflicts with the current status of the resource.
410	Gone The requested document is no longer available and the server does not know which address to redirect. It differs from 404 in that if 407 is returned, the document permanently leaves the specified position, and 404 indicates that the document is unavailable for unknown reasons.
411	Length required The server cannot process the request, unless the client sends a Content-Length header
412	Precondition failed Some prerequisites specified in the request header fail.
413	Request Entity too large The size of the target document exceeds the size that the server is willing to process. If the server thinks it can process the request later, it should provide a retry-after Header
414	Request-URI Too large Indicates that the URI is too long.
415	Unsupported media type Unsupported media type
416	Requested range not satisfiable The server cannot meet the range header specified by the customer in the request.
417	Expectation failed Execution failed
423	Locked Locked Error
424	Failed dependency
425	Unordered collection
426	Upgrade required
500	Internal Server Error The server encounters unexpected circumstances and cannot complete the customer's request: 500.12-the application is busy restarting on the Web server. 500.13-the Web server is too busy. 500.15-Direct Request to global. ASA is not allowed. The 500.16-unc authorization credential is incorrect. This error code is dedicated to IIS 6.0. 500.18-the URL-authorized storage cannot be opened. This error code is dedicated to IIS 6.0. 500.100-Internal ASP error.
501	Not Implemented The server does not support the functions required to implement the request. The header value specifies the unimplemented configuration. For example, the customer sends a put request not supported by the server.
502	Bad Gateway When the server acts as a gateway or proxy, in order to complete the request to access the next server, but the server returns an invalid response. In other words, when the web server is used as a gateway or proxy server, it receives an invalid response-502.1-CGI application timeout. · 502.2-CGI application error.
503	Service unavailable The service is unavailable, and the server fails to respond due to maintenance or heavy load. For example, Servlet may return 503 when the database connection pool is full. When the server returns 503, A retry-after header can be provided. This error code is dedicated to IIS 6.0
504	Gateway time-out The gateway times out and is used by the proxy or gateway server, indicating that the remote server cannot receive a response in a timely manner.
505	HTTP Version Not Supported The server does not support the HTTP Version specified in the request
506	Variant also negotiates
507	Insufficient storage
516	Not extended