HTTP status code overview and solution-PHP source code

Ec (2); you do not have sufficient execution permits. For example, if the directory permission of the & nbsp; ASP & nbsp; page to be accessed is set to & ldquo; none & rdquo;, or the & nbsp; CGI & nbsp; the directory permission of the script is & ldquo; only scripts & rdquo; are allowed. This error message is displayed. To modify the execution permission, right-click the directory in the & nbsp; Microsoft & nbsp; console & nbsp; (MMC) & nbsp, then, the orders are "script" ec (2) and "script" in sequence.

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.

403.3-write access is forbidden. Verify that the IIS permission and NTFS limit 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 this 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.

403.6-the IP address is rejected. The server configuration rejects access to your current IP address.

403.7-client certificate required. You have configured your server as a client authentication certificate, but you have not installed a valid client certificate.

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

403.9-too many users. The number of users connected to the server exceeds the number of connections set by IIS.

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.

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

500-internal server error. Common Causes of 500 errors include ASP syntax errors, ACCESS database connection statements errors, file references and inclusion paths errors, and the use of components not supported by the server, such as FSO.

500.12-server error: the application on the Web server 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.

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.

502-Gateway error. If the CGI script to be run does not return a valid HTTP header set, this error message is displayed.

1. Error No. 401.1-unauthorized: access is denied due to invalid creden. The user's anonymous access account (IUSR _ machine name by default) is disabled or has no permission to access the computer.

Solution:

(1) check whether the anonymous account set for site security in IIS manager is disabled. If yes, try the following methods to enable it:

Control Panel-> Administrative Tools-> Computer Management-> local users and groups, enable IUSR _ machine name account. If the problem persists, proceed to the next step.

(2) check whether the default anonymous access account of the site in the IIS manager or its group has the permission to access the server over the network in the Local Security Policy, if you have not attempted to grant permissions by following these steps:

Start-> Program-> Administrative Tools-> Local Security Policy-> local policy-> User permission assignment, double-click "Access this computer from network ", add default IIS users or their groups.

Note: Generally, custom IIS default anonymous access accounts belong to groups. To ensure security, follow this rule.

2. Error Code 401.2 HTTP Error 401.2-unauthorized: access is denied due to server configuration. Cause: anonymous authentication is disabled.

Solution:

Run inetmgr, choose site Properties> Directory Security> authentication and access control> enable Anonymous Access, enter the user name, or click browse to select a valid user, enter the password twice and then confirm.

3. Error code: 401.3 HTTP Error 401.3-unauthorized: access to requested resources is denied due to ACL settings.

Cause: IIS Anonymous Users generally belong to the Guests group, and we generally assign the permissions to store the website's hard disk only to the administrators group. In this case, according to the inheritance principle, website folders can only be accessed by members of the administrators group. As a result, the NTFS permission for anonymous IIS users to access this file is insufficient, and thus the page cannot be accessed.

100-indicates that part of the request has been received and the remaining part is being sent.

101-switch protocol.

2xx-success. The server successfully accepts the client request:

200-OK. The client request is successful.

201-created.

202-accepted.

203-non-authoritative information.

204-NO content.

205-Reset content.

206-part of content.

300-the server can perform multiple operations to receive requests.

301-permanent transfer and transfer. The requested content has been permanently moved to another new location.

302-Temporary Move transfer: the requested content has been moved to a new location temporarily.

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

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

400-Incorrect request.

401-Access denied. 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-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.4-require SSL.

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-request content not found.

404.0-the file or directory is not 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.

412-precondition failed.

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.

417-execution failed.

423-locking 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 server cannot complete the request.

502-the server received an invalid response when used as a gateway or proxy server.

502.1-CGI application timeout.

502.2-CGI application error.

503-the service is unavailable. This error code is dedicated to IIS 6.0.

504-gateway timeout.

505-the HTTP version is not supported.

Common HTTP status codes and their causes

200-successful. 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 instead of downloading the content from the server.

401.1-Logon Failed. Login Failed, possibly because the user name or password access is invalid.

401.3-Restrictions on resources in the service list are not authorized. This error may also occur if the NTFS permission problem exists or the file to be accessed has the corresponding permissions.

403.1-the execution access is forbidden.