The meaning and solution of the HTTP protocol status code

When the user is on the server of the Internet Information Service (IIS), the IIS server responds to the request and automatically returns a numeric code representing the status of the request, providing status information about the request. Also when the search engine spiders crawl in the process, the server will also be related to the HTTP status code, by understanding the HTTP status code, you can more detailed analysis of the log access.

100-Indicates that a portion of the request has been received and continues to send the remainder.

101-Switch protocol.

2XX-The successful server successfully accepted the client request.

200-OK. The client request was successful.

201-created.

202-accepted.

203-Non-authoritative information.

204-no content.

205-Reset the content.

206-part content.

300-The server can perform a variety of actions for incoming requests.

301-Permanent Move transfer, the requested content has been permanently moved to another new location.

302-temporary move transfer, the requested content has been temporarily moved to a new location

304-not modified. The requested content has not been modified since the last request.

307-Temporary redirection. The server is currently responding to requests from different locations, but the requester should continue to use the original location for subsequent requests.

400-the wrong request.

401-access is denied. IIS defines a number of different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log:

401.1-Login failed.

401.2-The server configuration caused the login to fail.

401.3-Authorization is not granted due to ACL restrictions on resources.

401.4-Filter Authorization failed.

401.5-ISAPI/CGI application authorization failed.

401.7-access is denied by the URL authorization policy on the WEB server. This error code is private to IIS 6.0.

403-Prohibit access: IIS defines a number of different 403 errors that indicate a more specific cause of the error:

403.1-execution access is prohibited.

403.2-Read access is forbidden.

403.3-Write access is forbidden.

403.4-Require SSL.

403.5-Requires SSL 128.

The 403.6-IP address was rejected.

403.7-Client certificate required.

403.8-site access is denied.

403.9-Excessive number of users.

403.10-Configuration is not valid.

403.11-Password change.

403.12-access to the mapping table is denied.

403.13-The client certificate was revoked.

403.14-Deny directory list.

403.15-Client access permission exceeded.

403.16-Client certificate is not trusted 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 private to IIS 6.0.

403.19-CGI cannot be performed for clients in this application pool. This error code is private to IIS 6.0.

403.20-passport Login failed. This error code is private to IIS 6.0.

404-The requested content was not found.

404.0-No files or directories were found.

404.1-The Web site cannot be accessed on the requested port.

The 404.2-web service extension lockout policy blocks this request.

The 404.3-mime mapping 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.

412-Prerequisite failed.

413-The request entity is too large.

414-The request URI is too long.

415-Unsupported media type.

416-The requested range is not satisfied.

417-Execution failed.

423-locked error.

500-Server Internal error.

500.12-The application is busy restarting on the WEB server.

The 500.13-web server is too busy.

500.15-Direct Request Global.asa is not allowed.

The 500.16-unc authorization credentials are incorrect. This error code is private to IIS 6.0.

The 500.18-url authorization store cannot be opened. This error code is private to IIS 6.0.

500.100-Internal ASP error.

501-The server was unable to complete the requested function.

502-The server received an invalid response when it was used as a gateway or proxy server.

The 502.1-cgi application timed out.

Error 502.2-cgi application.

503-The service is not available. This error code is private to IIS 6.0.

504-Gateway Timeout.

505-http version is not supported.

　　English version:
100:continue

101:switching protocols

102:processing

200:ok

201:created

202:accepted

203:non-authoriative Information

204:no Content

205:reset Content

206:partial Content

207:multi-status

300:multiple Choices

301:moved Permanently

302:found

303:see Other

304:not Modified

305:use Proxy

306: (Unused)

307:temporary Redirect

400:bad Request

401:unauthorized

402:payment granted

403:forbidden

404:file not Found

405:method not allowed

406:not acceptable

407:proxy Authentication Required

408:request time-out

409:conflict

410:gone

411:length Required

412:precondition Failed

413:request Entity Too Large

414:request-uri Too Large

415:unsupported Media Type

416:requested Range Not satisfiable

417:expectation Failed

422:unprocessable Entity

423:locked

424:failed Dependency

500:internal Server Error

501:not implemented

502:bad Gateway

503:service unavailable

504:gateway Timeout

505:http Version not supported

507:insufficient Storage

　　Common HTTP status Codes and why

200-success. IIS has successfully processed the sent request.

304-not modified. The content requested by the client is already in its cache and has not been modified since the cache. The client uses a cached copy of the content without downloading the content from the server.

401.1-Login failed. The login was unsuccessful, possibly because the user name or password access is not valid.

401.3-the list of services is limited to resources without authorization. Indicates that an NTFS permission problem exists. This error may also occur if you have the appropriate permissions for the file you are trying to access.

403.1-execution access is prohibited.

The following are two common causes of this error message:

You do not have sufficient permission to execute. For example, this error message appears if the directory where the ASP page you are attempting to access is set to none, or if you are trying to execute a CGI script that has permission to allow script only. To modify execution permissions, right-click the directory in Microsoft Management Console (MMC), and then click the Properties and Directories tab to ensure that the appropriate execution permissions are set for the content you are trying to access.

You did not set the script mapping of the file type you are trying to perform to identify the predicate you are using (for example, get or POST). To verify this, right-click the table of contents in MMC, click Properties, right-click the table of Contents tab, and configure, and then verify that the script mappings for the appropriate file type are set to allow the verbs that are used.

403.2-Read access is forbidden. Verify that IIS is set to allow read access to the directory. Also, if you are using the default file, verify that the file exists.

403.3-Write access is forbidden. Verify that the IIS permissions and NTFS limits are set to grant write access to the directory.

403.4-require SSL. Disable the Require Secure channel option or use HTTPS instead of HTTP to access the page.

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.

The 403.6-IP address was rejected. The server configuration denied access to your current IP address.

403.7-Client certificate required. You have configured your server to require a client authentication certificate, but you do not have a valid client certificate installed.

403.8-site access is denied. You have set a domain name limit for the domain that you use to access the server.

403.9-Excessive number of users. The number of users connected to this server exceeds the number of connections that IIS has set.

403.12-access to the mapping table is denied. The page you are trying to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied access to the file.

404-not found. This error occurs because the file you are trying to access has been moved or deleted.

500-Internal server error. Common causes of 500 errors are: ASP syntax error, Access database connection statement error, file reference and include path error, using the server does not support components such as FSO, etc.

500.12-Server Error: The application on the WEB server is rebooting. This means that you are attempting to load an ASP page while IIS restarts the application. This information disappears when the page is refreshed. If the page is refreshed, this information appears again, possibly because antivirus software is scanning the Global.asa file.

500-100.asp-asp error. This error message appears if an ASP page that you are trying to load contains an error code. To get a more accurate error message, disable the friendly HTTP error message. By default, this error message is enabled only on the default Web site.

502-Gateway error. This error message appears if the CGI script you are trying to run does not return a valid set of HTTP headers.

1, error number 401.1-Unauthorized: Access is denied due to invalid credentials. Because the user is using anonymous access to the account (the default is the IUSR_ machine name) is disabled, or does not have access to the computer, will cause users inaccessible.

Solution:

(1) To see if the anonymous account for site security settings in IIS Manager is disabled, and if so, try to enable it in the following ways:

Control Panel-> Management tools-> Computer Management-> Local Users and groups, enable IUSR_ machine name account. If it is not resolved, proceed to the next step.

(2) View the default anonymous access account for the site in IIS Manager or the group to which it belongs, in the local security policy, if there is no attempt to grant permissions with the following steps:

Start-> program-> Administrative Tools-> Local Security Policy-> security Policy-> Local policy-> User rights Assignment, double-click "Access this computer from the network" to add the IIS default user or the group to which it belongs.

Note: The general custom IIS default anonymous access account belongs to the group, and for security, there are no special needs, please follow this rule.

2, error number 401.2 HTTP error 401.2-Unauthorized: Access is denied due to server configuration. Reason: Anonymous authentication was turned off

Solution:

Run inetmgr, open the Site Properties-> Directory Security-> authentication and access control-> Select Enable Anonymous access, enter a username, or click "Browse" to select a legitimate user, and then confirm the password two times.

3, Error number: 401.3 HTTP error 401.3-Unauthorized: Access due to the ACL on the requested resource settings are denied.

Reason: IIS anonymous users generally belong to the Guests group, and we generally put the site's hard drive to the Administrators group, at this time, in accordance with the principle of inheritance, the site folder only members of the Administrators group can access, Insufficient NTFS permissions to access the file by IIS anonymous users, causing the page to be inaccessible.

Solution: Access to the Web site folder for IIS anonymous users by accessing the security options for the folder, adding IIS anonymous users, and giving them the appropriate permissions, generally read and write.