Shulou(Shulou.com)05/31 Report--

This article mainly explains "what are the IIS status codes of Internet information server". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "what are the Internet information server IIS status codes"!

When a user surfing the web tries to access content on a server running Internet Information Services (IIS) through HTTP or File transfer Protocol (FTP), IIS returns a numeric code indicating whether the attempt was successful or failed. The status code is recorded in the IIS log and may also be displayed in a Web browser or FTP client. The status code may also indicate the exact reason why the request failed.

The IIS administrator can customize the error message that will be displayed in the user's Web browser when the request fails.

HTTP

1xx-Information Tip

These status codes represent temporary responses. The client should be prepared to receive one or more 1xx responses before receiving a regular response.

100-go on.

101-switch protocol.

2xx-successful

This type of status code indicates that the 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-resets the content.

206-partial content.

207Polymorphism (WebDAV).

3xx-redirect

The client browser must do more to implement the request. For example, a browser may have to request a different page on the server or repeat the request through a proxy server.

301-permanently moved

302-the object has moved.

304-not modified.

307-temporary redirection.

4xx-client error

An error has occurred and there seems to be a problem with the client. For example, the client requests a page that does not exist and the client does not provide valid authentication information.

400-wrong request.

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

401.1-login failed.

401.2-the server configuration caused the login failure.

401.3-not authorized due to resource restrictions imposed by ACL.

401.4-filter authorization failed.

401.5-ISAPI/CGI application authorization failed.

401.7-access is denied by the URL authentication policy on the Web server. This error code is specific to IIS 6. 0.

Forbidden access: IIS defines several different 403 errors to indicate a more specific cause of the error:

403.1-Executive access is prohibited.

403.2-read access is prohibited.

403.3-write access is prohibited.

403.4-SSL is required.

403.5-SSL 128 is required.

403.6-the IP address is rejected.

403.7-client certificate is required.

403.8-site access is denied.

403.9-too many users.

403.10-invalid configuration.

403.11-password change.

403.12-access to the mapping table is denied.

403.13-the client certificate is revoked.

403.14-reject directory list.

403.15-client access permission exceeded.

403.16-the client certificate is not trusted or invalid.

403.17-the client certificate has expired or is not yet valid.

403.18-the requested URL cannot be executed in the current application pool. This error code is specific to IIS 6. 0.

403.19-CGI cannot be executed for clients in this application pool. This error code is specific to IIS 6. 0.

403.20-Passport login failed. This error code is specific to IIS 6. 0.

404-not found.

404.0-(none)-No files or directories were found.

404.1-the website cannot be accessed through the requested port.

404.2-the Web service extension locking policy blocks this request.

The 404.3-MIME mapping policy blocks this request.

405-the HTTP predicate used to access this page is not allowed (method is not allowed)

406-the client browser does not accept the MIME type of the requested page.

407-proxy authentication is required.

412-prerequisites failed.

413-the request entity is too large.

414-request URI is too long.

415-unsupported media type.

416-unable to meet the scope of the request.

417-execution failed.

423-Lock error.

5xx-Server error

The server was unable to complete the request because it encountered 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 for Global.asa is not allowed.

500.16-the UNC authorization credentials are incorrect. This error code is specific to IIS 6. 0.

500.18-unable to open the URL authorization store. This error code is specific to IIS 6. 0.

500.19-the data for this file is not configured correctly in the Metabase.

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-the CGI application timed out.

502.2-an error occurred in the CGI application.

503-the service is not available. This error code is specific to IIS 6. 0.

504-the gateway timed out.

Version 505-HTTP is not supported.

IIS HTTP status Code and its reason

200-success. This status code indicates that IIS successfully processed the request.

206-partial content. This indicates that a file has been partially downloaded. You can renew a corrupted download or split the download into multiple concurrent streams.

207Polymorphism (WebDAV). This message should be preceded by a XML message that may contain several separate response codes, depending on how many sub-requests are made.

301-permanently moved. This request and all subsequent requests should go to the specified URI.

302-found. For form-based authentication, this message is usually expressed as "object moved." The requested resource temporarily resides in a different URI. Because redirection can sometimes change, the client should continue to use Request-URI when requesting it in the future. This response can be cached only if indicated in the Cache-Control or Expires header field.

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 a cached copy of the document instead of downloading the document from the server.

401.1 and 401.2-login failed. The login attempt failed because the user name or password is not valid, or there is a problem with the system configuration. For more information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

907273 (http://support.microsoft.com/kb/907273/) troubleshoot HTTP 401errors in IIS

401.3-not authorized due to resource restrictions imposed by ACL. This indicates that there is a NTFS permission problem. This error can occur even if you have the appropriate permissions on the file you are trying to access. For example, if the IUSR account does not have access to the C:\ Winnt\ System32\ Inetsrv directory, you will see this error. For more information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

271071 (http://support.microsoft.com/kb/271071/) how to set the required NTFS and user permissions for the IIS Web server

Default permissions and user permissions for 812614 (http://support.microsoft.com/kb/812614/) IIS 6.0

403-No access: if the site does not have a default document set and is not set to allow directory browsing, you will receive this general 403 status code. For more information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

320051 (http://support.microsoft.com/kb/320051/) how to configure default documents in Internet Information Services

403.1-Executive access is prohibited. Here are two common reasons for this error message:

You do not have sufficient enforcement permission. For example, this error message appears if the directory permission of the ASP page you are trying to access is set to none, or if the directory permission of the CGI script you are trying to execute is allow scripts only. To modify the execution permissions, right-click the directory in the Microsoft Management console (MMC), and then click the Properties tab, and then click the 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 execute to identify the predicates used (for example, GET or POST). To verify this, right-click the directory in the Microsoft administrative console, click the Properties tab, click configuration, and then verify that the script mapping for the appropriate file type is set to the verbs that are allowed to be used.

403.2-read access is prohibited. Verify that IIS is set to allow read access to directories. In addition, if you are using the default file, verify that the file exists. For additional information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

247677 (http://support.microsoft.com/kb/247677/) error message: 403.2 Forbidden: Read Access Forbidden (403.2 prohibited access: read access prohibited)

403.3-write access is prohibited. Verify that the IIS and NTFS permissions are set to grant write access to the directory. For additional information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

248072 (http://support.microsoft.com/kb/248072/) error message: 403.3 Forbidden: Write Access Forbidden (403.3 prohibited access: write access prohibited)

403.4-SSL is required. Disable the require secure channel option, or use HTTPS instead of HTTP to access the page. If this error occurs on a website that does not have a certificate installed, click the article number below to view the appropriate article in the Microsoft knowledge base:

Error message in 224389 (http://support.microsoft.com/kb/224389/) Internet Information Server 403.5: "HTTP Error 403, 403.4, 403.5 Forbidden:SSL Required" (HTTP errors 403, 403.4, 403.5 prohibited: SSL required)

403.5-SSL 128 is required. Disable the option that requires 128-bit encryption, or use a browser that supports 128-bit encryption to view the page.

403.6-the IP address is rejected. You have configured the server to deny access to your current IP address. For additional information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

248043 (http://support.microsoft.com/kb/248043/) error message: 403.6-Forbidden:IP Address Rejected (403.6-unavailable: IP address rejected)

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

186812 (http://support.microsoft.com/kb/186812/) PRB: error message: 403.7 Forbidden: Client Certificate Required (403.7 No access: client certificate required)

403.8-site access is denied. You have set domain name restrictions for the domain used to access the server. For additional information about how to resolve this issue, click the article number below to view the appropriate article in the Microsoft knowledge Base:

248032 (http://support.microsoft.com/kb/248032/) error message: Forbidden: Site Access Denied 403.8 (access prohibited: site denied access 403.8)

403.9-too many users. The number of users connected to this server exceeds the connection limit you set. For additional information about how to change this limit, click the article number below to view the appropriate article in the Microsoft knowledge Base:

248074 (http://support.microsoft.com/kb/248074/) error message: Access Forbidden:Too Many Users Are Connected 403.9 (access prohibited: too many users connected 403.9)

Note: Microsoft Windows 2000 Professional and Windows XP Professional automatically set a limit of up to 10 connections on IIS. You cannot change this limit.

403.12-access to the mapping table is denied. The page you want to access requires a client certificate. However, the user ID who is mapped to the client certificate has denied access to the file. For additional information, click the article number below to view the appropriate article in the Microsoft knowledge base:

248075 (http://support.microsoft.com/kb/248075/) error: HTTP 403.12-Access Forbidden: Mapper Denied Access (HTTP 403.12-access prohibited: mapper denied access)

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 try to access a file with a limited extension after installing the URLScan tool. If you install the URIScan tool, you will see "Rejected by URLScan" in the w3svc log file. In this case, the word "Rejected by URLScan" appears in the log file entry of the request. For more information, click the article number below to view the appropriate article in the Microsoft knowledge base:

Common causes of 248033 (http://support.microsoft.com/kb/248033/) IIS server returning "HTTP 404-File not found" (HTTP 404-file not found) error

404.1-the website cannot be accessed through the requested port. This error message indicates that the IP address of the website you are trying to access does not accept requests from the port used for this request. For more information, click the article number below to view the appropriate article in the Microsoft knowledge base:

248034 (http://support.microsoft.com/kb/248034/) IIS error: 404.1 Web Site Not Found (404.1 site not found)

404.2-lockout policy blocked this request. In IIS 6. 0, this means that the request has been blocked in the Web service extension list. For more information, click the article number below to view the appropriate article in the Microsoft knowledge base:

How to add and remove Web service extension files in IIS 328419 (http://support.microsoft.com/kb/328419/)

How to list Web service extensions and extension files in IIS 328505 (http://support.microsoft.com/kb/328505/)

328360 (http://support.microsoft.com/kb/328360/) how to enable and disable ISAPI extensions and CGI applications in IIS

The 404.3-MIME mapping policy blocks this request. This problem occurs if the following conditions exist:

The handler mapping for the requested file extension is not configured.

There is no corresponding MIME type configured for the Web site or application.

405-method that is not allowed. This error occurs when the client sends a HTTP request to the server running IIS and the request contains a HTTP verb that the server does not recognize. To resolve this issue, make sure that the client requests use HTTP rfc-compatible HTTP verbs. For information about HTTP rfc, see the reference section.

500-Internal server error. Many server-side errors can cause this error message. The event Viewer log contains more detailed reasons for the error. In addition, you can disable friendly HTTP error messages to receive a detailed error description. For more information about how to display friendly HTTP error messages, click the article number below to view the appropriate article in the Microsoft knowledge base:

294807 (http://support.microsoft.com/kb/294807/) HOW TO: Disable Internet Explorer 5 'Show Friendly HTTP Error Messages' Feature on the Server Side

500.12-the application is being restarted. This means that you are trying to load the ASP page while IIS is restarting the application. When the page is refreshed, this message disappears. If this message appears again after refreshing the page, it may be that the antivirus software is scanning the Global.asa file. For additional information, click the article number below to view the appropriate article in the Microsoft knowledge base:

248013 (http://support.microsoft.com/kb/248013/) error message: HTTP Error 500-12 Application Restarting (HTTP error 500-12 application is restarting)

500-100.ASP-ASP error. This error message appears if the ASP page you are trying to load contains an error code. To get a more accurate error message, disable friendly HTTP error messages. By default, this error message is enabled only on the default Web site. For additional information about how to see this error message on a website that is not the default, click the article number below to view the appropriate article in the Microsoft knowledge Base:

261200 (http://support.microsoft.com/kb/261200/) displays HTTP 500error messages instead of ASP error messages for 500-100.asp

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. To resolve this problem, you must debug the CGI application to determine why it passes invalid HTTP information to IIS.

503-the service is not available. Starting with IIS 6, kernel-mode Http.sys components generate HTTP 503 states. For more information about how to identify and troubleshoot HTTP 503 errors, click the article number below to view the appropriate article in the Microsoft knowledge base:

Error logging in 820729 (http://support.microsoft.com/kb/820729/) HTTP API

500.19. You will receive this error if the XML Metabase contains invalid configuration information in the type of content you are trying to access. To resolve this issue, delete or correct an invalid configuration. This problem usually indicates a problem with the ScriptMap Metabase key.

FTP

1xx-preliminary answer in the affirmative

These status codes indicate that an operation has started successfully, but the client wants another reply before continuing with the new command.

110 restart mark reply.

The 120 service is ready and will start in nnn minutes.

125 data connection is open and transfer is starting.

150 file status is normal, ready to open data connection.

2xx-Yes, complete the reply

An operation has been completed successfully. The client can execute the new command.

Command 200 is confirmed.

202 commands were not 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.

The NAME system type, where NAME is the official system name listed in the Assigned Numbers document.

220 the service is ready to execute requests from new users.

221 the service closes the control connection. If appropriate, please log out.

225 the data connection is open and there is no transmission in progress.

226 close the data connection. The requested file operation was successful (for example, transfer or discard files).

227 enter passive mode (h 2, recital, h3, recital, h4, p5, p1, p2).

230 users are logged in and continue.

250 the requested file operation is correct and completed.

257 "PATHNAME" has been created.

3xx-affirmative intermediate answer

The command succeeded, but the server needs more information from the client to complete the processing of the request.

331 the user name is correct and a password is required.

332 A login account is required.

350 the requested file operation is waiting for further information.

4xx-transient negative completion reply

The command was unsuccessful, but the error was temporary. If the client retries the command, it may execute successfully.

421 service is not available, closing control connection. If the service determines that it must be shut down, this reply will be sent to any command.

425 unable to open the data connection.

426 Connection closed; transfer aborted.

450 the requested file operation was not performed. The file is not available (for example, the file is busy).

451 the requested operation terminated abnormally: a local error is being processed.

452 the requested operation was not performed. There is not enough storage space in the system.

5xx-permanently negative completion reply

The command was unsuccessful and the error is permanent. If the client retries the command, the same error will occur again.

500 syntax error, the command is not recognized. This may include errors such as command line being too long.

501 has a syntax error in the parameter.

502 the command was not executed.

503 wrong command sequence.

504 the command for this parameter was not executed.

530 not logged in.

532 an account is required to store files.

550 the requested operation was not performed. The file is not available (for example, no file found, no access).

551 the requested operation terminated abnormally: unknown page type.

552 the requested file operation terminated abnormally: storage allocation exceeded (for the current directory or dataset).

553 the requested operation was not performed. Disallowed file name.

Common FTP status codes and their causes

150-FTP uses two ports: 21 for sending commands and 20 for sending data. The status code 150 indicates that the server is ready 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 transferring files. The operation completed successfully and the data connection was closed.

230-the status code is displayed after the client sends the correct password. It indicates that the user has successfully logged in.

331-after the client sends the user name, the status code is displayed. The status code is displayed regardless of whether the user name provided is a valid account in the system.

426-commands to open a data connection to perform an operation, but the operation has been cancelled and the data connection has been closed.

530-this status code indicates that the user cannot log in because the username and password combination is not valid. If you log in with a user account, you may type the wrong user name or password, or you may choose to allow anonymous access only. If you log in using an anonymous account, the configuration of IIS may deny anonymous access.

550-the command was not executed because the specified file is not available. For example, the file you want to GET does not exist, or you try to PUT the file to a directory that you do not have write permission to.

At this point, I believe that everyone on the "Internet information server IIS status code what" have a deeper understanding, might as well to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.