Http status code (200, 404, 500, etc.) (to CSDN), 500 and other csdn
When we send a request from a client to the server
The server returns the status code to us.
The status code is the status of the server response.
Through this, we can know whether the current request is successful or what problems have occurred.
A Status Code consists of three digits and a reason phrase (for example, the most common one is 200 OK)
The first number indicates the response category. The response category is divided into five types from 1 to 5.
Add: Actually, I found that there is another 600 Unparseable Response Headers with six Headers.
It indicates that the server does not return the response header, but only returns the entity content. It is also regarded as a server error status code, but it is definitely not common.
||Information Status Code (Informational)
||The server is processing the request
||The request has been processed properly.
||Additional operations are required to complete the request
||Client Error code)
||The server cannot process the request due to client reasons
||Server Error Code)
||An error occurred while processing the request due to server reasons
The definition of the status code response category must be followed, and the subsequent two digital servers are no problem for DIY.
RFC2616 (document used to specify HTTP protocol standards) is defined by more than 40 standards, and up to 60 extensions can be added.
However, there are only about 14 common HTTP status codes. Let's talk about these 14 representative HTTP status codes.
100 Continue continues. Generally, when a post request is sent, the server returns this message after the http header is sent, indicating confirmation and then sending specific parameter information.
200 OK normal return information
201 The Created request is successful and the server creates a new resource.
202 The Accepted server has Accepted the request but has not processed it.
301 the webpage requested by Moved Permanently has been Permanently Moved to a new location.
302 Found temporary redirection.
303 See Other temporary redirection, and always use GET to request a new URI.
304 Not Modified the requested webpage has Not been Modified since the last request.
400 the Bad Request server cannot understand the Request format. The client should not try to use the same content to initiate a Request again.
401 Unauthorized request is Unauthorized.
403 Forbidden access is prohibited.
404 Not Found cannot find the resource that matches the URI.
500 Internal Server Error the most common Server errors.
503 the Service Unavailable server cannot process the request temporarily (possibly overload or maintenance ).
Covers all issues
HTTP 400-invalid request
HTTP 401.1-unauthorized: Logon Failed
HTTP 401.2-unauthorized: logon fails due to server configuration problems
HTTP 401.3-ACL prohibit Resource Access
HTTP 401.4-unauthorized: Authorization denied by filter
HTTP 401.5-unauthorized: ISAPI or CGI authorization failed
HTTP 403-Access prohibited
HTTP 403-access to Internet service manager is limited to Localhost
HTTP 403.1 Prohibit Access: Prohibit executable access
HTTP 403.2-Access prohibited: Read prohibited
HTTP 403.3-Access prohibited: Write Access prohibited
HTTP 403.4-Access prohibited: requires SSL
HTTP 403.5-Access prohibited: requires SSL 128
HTTP 403.6-Access prohibited: the IP address is denied
HTTP 403.7-Access prohibited: client certificate required
HTTP 403.8-Access prohibited: site access prohibited
HTTP 403.9-Access prohibited: too many connected users
HTTP 403.10-Access prohibited: Invalid Configuration
HTTP 403.11-Access prohibited: Password Change
HTTP 403.12-Access prohibited: mappers reject access
HTTP 403.13-Access prohibited: the client certificate has been revoked
HTTP 403.15-Access prohibited: too many access permits from customers
HTTP 403.16-Access prohibited: the client certificate is untrusted or invalid
HTTP 403.17-Access prohibited: the client certificate has expired or has not yet taken effect HTTP 404.1-
The Web site cannot be found.
HTTP 404-file not found
HTTP 405-the resource is forbidden
HTTP 407-proxy authentication required
HTTP 410-never available
HTTP 412-precondition failed
HTTP 414-request-URI is too long
HTTP 500-Internal Server Error
HTTP 500.100-Internal Server Error-ASP Error
HTTP 500-11 Server Disabled
HTTP 500-12 Application restart
HTTP 500-13-the server is too busy
HTTP 500-14-invalid Application
HTTP 500-15-requests to global. asa are not allowed
Error 501-not implemented
HTTP 502-Gateway error
When a user attempts to access content on a server running Internet Information Service (IIS) through HTTP or file transfer protocol (FTP), IIS returns a digital code indicating the status of the request. This status code is recorded in IIS logs and may also be displayed in a Web browser or an FTP client. The status code can indicate whether the request is successful or not, and reveal the exact cause of the Request failure.
Log File Location
By default, IIS stores its log files in the % WINDIRSystem32Logfiles folder. Each WWW site and FTP site have a separate directory under this directory. By default, log files are created in these directories every day and named by date (for example, exYYMMDD. log ).
These status codes indicate temporary responses. Before receiving a regular response, the client should be prepared to receive one or more 1xx responses. 100-continue.
This type of Status Code indicates that the server successfully accepts client requests.
200-OK. The client request is successful.
206-part of content.
The client browser must perform more operations to implement the request. For example, the browser may have to request different pages on the server or repeat the request through the proxy server.
302-the object has been moved.
The client seems to be faulty when an error occurs. For example, the client does not provide valid authentication information for a page that does not exist in a request. 400-Incorrect request.
401-Access denied. IIS defines many different
401 errors, which indicate more specific causes of errors. These specific error codes are displayed in the browser but not in the IIS log:
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-An error occurred while authorizing the ISAPI/CGI application.
401.7-the access is rejected by the URL Authorization Policy on the Web server. This error code is dedicated to IIS 6.0.
403-Access prohibited: IIS defines many different 403 errors, which indicate more specific error causes:
403.1-the execution access is forbidden.
403.2-Read access is forbidden.
403.3-write access is forbidden.
403.5-require SSL 128.
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 this 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. 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-HTTP predicates used to access this page are not allowed (methods are not allowed)
406-the client browser does not accept the MIME type of the requested page.
407-proxy authentication is required.
413-The Request Entity is too large.
414-the request URI is too long.
415-unsupported media type.
416-the requested range cannot be met.
The server cannot complete the request because of an error.
500-internal server error.
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-the header value specifies the unimplemented configuration.
502-the Web server received an invalid response when used as a gateway or proxy server.
502.1-CGI application timeout.
502.2-CGI application error. Application.
503-the service is unavailable. This error code is dedicated to IIS 6.0.
505-the HTTP version is not supported.
Common HTTP status codes and their causes
200-successful. This status code indicates that IIS has successfully processed the request.
304-not modified. The document requested by the client is already in its cache and has not been modified since the cache. The client uses cached copies of documents instead of downloading documents from the server.
401.1-Logon Failed. The logon attempt fails, possibly because the user name or password is invalid.
401.3-the ACL is not authorized due to resource restrictions. This indicates that NTFS permission issues exist. This error may occur even if you have the relevant permissions on the file you are trying to access. For example, if the IUSR account does not have access to the C: WinntSystem32Inetsrv directory, you will see this error. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
187506 INFO: Basic NTFS permission for IIS 4.0
403.1-the execution access is forbidden. The following are two common causes of this error: you do not have sufficient execution permits. For example, if the directory permission of the ASP page to be accessed is set to "NONE", or the directory permission of the CGI script to be executed is "only allow scripts ", this error message is displayed. To modify the execution permission, right-click the directory in the Microsoft Management Console (MMC), and then click the properties and directory tabs to ensure that the appropriate execution permission is set for the content to be accessed.
You have not set the script ing of the file type you are trying to execute to identify the predicates used (for example, GET or POST ). To verify this, right-click the directory in MMC, click Properties, Directory tab, and configuration, and then verify that the script ing of the corresponding file type is set to allow the predicates to be used.
403.2-Read access is forbidden. Verify that IIS has been set to allow read access to the directory. In addition, if you are using a default file, verify that the file exists. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
247677 error message: 403.2 Forbidden: Read Access Forbidden (403.2 Access prohibited: Read Access prohibited)
403.3-write access is forbidden. Verify that the IIS and NTFS permissions are set to grant write access to the directory. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
248072 error message: 403.3 Forbidden: Write Access Forbidden (403.3 Access prohibited: Write Access prohibited)
403.4-require SSL. Disable the require security channel option, or use HTTPS instead of HTTP to access the page. If this error occurs on a Web site that does not have a certificate installed, click the following article number to view the article in the Microsoft Knowledge Base:
224389 error message: HTTP errors 403, 403.4, 403.5 Prohibit Access: require SSL
403.5-require SSL 128. Disable the require 128-bit encryption option, or use a browser that supports 128-bit encryption to view the page. If this error occurs on a Web site that does not have a certificate installed, click the following article number to view the article in the Microsoft Knowledge Base:
224389 error message: HTTP errors 403, 403.4, 403.5 Prohibit Access: require SSL
403.6-the IP address is rejected. You have configured your server to deny access to your current IP address. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
248043 error message: 403.6-Forbidden: IP Address Rejected (403.6-unavailable: IP Address denied)
403.7-client certificate required. You have configured your server as a client authentication certificate, but you have not installed a valid client certificate. For other information, click the following article number to view the article in the Microsoft Knowledge Base:
190004 error 403.7 or "Connection to Server cocould Not Be Established" (Connection to Server cannot Be Established)
186812 PRB: error message: 403.7 Forbidden: Client Certificate Required (403.7 Access prohibited: Client Certificate Required)
403.8-site access is denied. You have set domain name restrictions for the domain you use to access the server. For more information about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
248032 error message: Forbidden: Site Access Denied 403.8 (Forbidden Access: Site Access Denied 403.8)
403.9-too many users. The number of users connected to the server exceeds the connection limit you set. For more information about how to change this restriction, click the following article number to view the article in the Microsoft Knowledge Base:
248074 error message: Access Forbidden: Too already Users Are Connected 403.9 (Forbidden Access: Too Many Connected Users: 403.9)
Note: Microsoft Windows 2000 Professional and Microsoft Windows XP Professional automatically set a maximum of 10 connections on IIS. You cannot change this restriction.
403.12-access to the ing table is denied. The client certificate is required for the page to be accessed, but the user ID mapped to your client certificate has been denied access to the file. For other information, click the following article number to view the article in the Microsoft Knowledge Base:
248075 error message: HTTP 403.12-Access Forbidden: Mapper Denied Access (HTTP 403.12-Access prohibited: ing Table Access Denied)
404-not found. This error occurs because the file you are trying to access has been removed or deleted. This error also occurs if you attempt to access a file with a limited extension after installing the URLScan tool. In this case, "Rejected by URLScan" appears in the log file of the request.
500-internal server error. Many server errors may cause this error message. The Event Viewer log contains more detailed error causes. In addition, you can disable the friendly HTTP Error message to receive detailed error descriptions. For more information about how to disable HTTP-friendly error messages, click the following article number to view the article in the Microsoft Knowledge Base:
294807 how to disable the "show friendly HTTP Error messages" function of Internet Explorer 5 on the server side
500.12-the application is restarting. This indicates that you attempt to load ASP pages When IIS restarts the application. After the page is refreshed, this information disappears. If this information appears again after the page is refreshed, it may be that the anti-virus software is scanning the Global. asa file. For other information, click the following article number to view the article in the Microsoft Knowledge Base:
248013 Error message: HTTP Error 500-12 Application Restarting (HTTP Error 500-12 Application Restarting)
500-100.ASP-ASP error. If the ASP page to be loaded contains the error code, this error message is displayed. To obtain more accurate error information, disable the friendly HTTP error message. By default, this error message is only enabled on the default Web site. For more information about how to view this error message on a non-default Web site, click the following article number to view the article in the Microsoft Knowledge Base:
261200: HTTP 500 error message is displayed, but ASP error message of 500-100.asp is not displayed.
502-Gateway error. If the CGI script to be run does not return a valid HTTP header set, this error message is displayed.
1xx-Affirmative preliminary reply
These status codes indicate that an operation has started successfully, but the client wants to receive another response before continuing to operate the new command. 110 restart mark the reply.
120 the service is ready and starts in nnn minutes.
125 the data connection is enabled and transmission is starting.
150 the file is in normal state and you are ready to open the data connection.
2xx-a positive response
An operation has been completed successfully. The client can execute new commands. 200 command OK.
202 if no command is executed, there are too many commands on the site.
211 system status or system help reply.
212 directory status.
213 File status.
214 help message.
215 NAME system type, where NAME is the formal system NAME listed in the Assigned Numbers document.
220 the service is ready to execute new user requests.
221 close the control connection. If appropriate, log out.
225 the data connection is opened and there is no transmission in progress.
226 close the data connection. The requested file operation has been successful (for example, transferring a file or dropping a file ).
227 enter the passive mode (h1, h2, h3, h4, p1, p2 ).
230 The user has logged on and continues.
250 the requested file operation is correct and has been completed.
257 "PATHNAME" has been created ".
3xx-Affirmative intermediate reply
The command is successful, but the server needs more information from the client to process the request. 331 the user name is correct and the password is required.
332 You need to log on to the account.
350 the requested file operation is waiting for further information.
4xx-completion of transient Negation
The command fails, but the error is temporary. If the client retries the command, it may be executed successfully.
421 the service is unavailable and the control connection is being closed. If the Service determines that it must be disabled, this response will be sent to any command.
425 data connection cannot be enabled.
426 Connection closed; transfer aborted.
450 file operations not requested. The file is unavailable (for example, the file is busy ).
451 request operation exception termination: processing local error.
452 the requested operation is not performed. Insufficient system storage space.
5xx-permanent completion reply
The command fails. The error is permanent. If the client retries the command, the same error will occur again.
500 syntax error. The command cannot be identified. This may include errors such as too long command lines.
501 syntax error in the parameter.
502 the command is not executed.
503 error command sequence.
504 the command for this parameter is not executed.
530 not logged on.
532 accounts are required to store files.
550 the requested operation is not performed. File is unavailable (for example, the file is not found and no access permission is available ).
551 exceptional request termination: Unknown page type.
552 the requested file operation ended abnormally: exceeds Storage Allocation (for the current directory or dataset ).
553 the requested operation is not performed. The file name is not allowed.
Common FTP status code and Its Causes
150-FTP uses two ports: 21 for sending commands and 20 for sending data. Status Code 150 indicates that the server is preparing to open a new connection on Port 20 and send some data.
226-the command opens a data connection on Port 20 to perform operations, such as file transfer. This operation is successfully completed and the data connection is closed.
230-the status code is displayed after the client sends the correct password. It indicates that the user has successfully logged on.
331-the status code is displayed after the client sends the user name. This status code is displayed no matter whether the user name is a valid account in the system.
426-the command opens the data connection to perform the operation, but the operation has been canceled and the data connection has been closed.
530-the status code indicates that the user cannot log on because the combination of the user name and password is invalid. If you log on with a user account, you may enter the wrong user name or password, or you may choose to allow anonymous access only. If you log on with an anonymous account, the IIS configuration may reject anonymous access.
550-the command is not executed because the specified file is unavailable. For example, the file to GET does not exist, or you try to PUT the file to a directory without the write permission.
Come on, avoid recognizing http status codes, and get laughed at for half a day.