Encyclopedia HTTP error 403 401,400,404,304,200
HTTP 400 - Bad Request
HTTP 401.1 - Unauthorized: Logon failed
HTTP 401.2 - Unauthorized: server configuration Logon failed due to
HTTP 401.3 - ACL prohibit access resources
HTTP 401.4 - Unauthorized: authorization is filters to refuse
HTTP 401.5 - Unauthorized: ISAPI or CGI authorized failure
HTTP 403 - Forbidden
HTTP 403 - Access to Internet Services Manager is limited to Localhost
HTTP 403.1 - Forbidden: Access is prohibited perform
HTTP 403.2 - Forbidden: Read access is prohibited
HTTP 403.3 - Forbidden: Write disabled access
HTTP 403.4 - Forbidden : requires SSL
HTTP 403.5 - Forbidden: requires SSL 128
HTTP 403.6 - Forbidden: IP address rejected
HTTP 403.7 - Forbidden: require customers to certificate
HTTP 403.8 - Forbidden: ban site visit
HTTP 403.9 - Forbidden: connecting users too multi-
HTTP 403.10 - Forbidden: configuration invalid
HTTP 403.11 - Forbidden: password change
HTTP 403.12 - Forbidden: mapper denied access to
HTTP 403.13 - Forbidden: client certificate has been revoked
HTTP 403.15 - Forbidden: client access Licenses excessive
HTTP 403.16 - Forbidden: client certificate untrusted or invalid
HTTP 403.17 - Forbidden: client certificate has expired or is not yet valid HTTP 404.1 -
Can not find Web site
HTTP 404- File not found
HTTP 405 - Resource prohibited
HTTP 406 - can not accept
HTTP 407 - Proxy authentication required
HTTP 410 - forever unavailable
HTTP 412 - a prerequisite for failure
HTTP 414 - Request - URI is too long
HTTP 500 - internal server error
HTTP 500.100 - internal server error - ASP error
HTTP 500-11 server to shut down
HTTP 500-12 application restart
HTTP 500-13 - server too busy
HTTP 500-14 - the application is invalid
HTTP 500-15 - not allowed request Global.asa
error 501 - unimplemented
HTTP 502 - gateway error
When the user attempts to access content on a server that is running Internet Information Services (IIS) is a through HTTP or File Transfer Protocol (FTP), IIS returns a numeric code that represents the status of the request. This status code is recorded in the IIS log, and may also appear in the Web browser or FTP client. Status code can indicate whether a particular request is successful, it can also reveal the exact reason for the request failed.
Location of log files
By default, IIS log files on it% WINDIRSystem32Logfiles folder. Each World Wide Web (WWW) site and FTP site has a separate directory in the directory. By default, the log file is created every day in these directories, and log files are named with the date to (eg, exYYMMDD.log).
HTTP
1xx - Information Tips
These status codes indicate a provisional response. Before a client receiving a regular response, should be prepared to receive one or more 1xx response. • 100 - continue.
• 101 - Switching protocols.
2xx - Success
Such status codes indicate that the server successfully accepted the client request. • 200 - OK. The client request has succeeded.
• 201 - has been created.
• 202 - Accepted.
• 203 - Non-authoritative information.
• 204 - No content.
• 205 - Reset content.
• 206 - part of the contents.
3xx - Redirection
The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server or repeat the request through a proxy server. • 302 - Object moved.
• 304 - Not Modified.
• 307 - Temporary redirect.
4xx - Client Error
Error occurs, the client seems to have problems. For example, a client requests a page that does not exist, the client may not provide valid authentication information. • 400 - Bad Request.
• 401 - Access denied. IIS defines a number of different 401 errors that indicate a more specific cause of the error. These specific error code is displayed in the browser, but not in the IIS log: • 401.1 - Logon failed.
• 401.2 - Logon failed due to server configuration.
• 401.3 - due to ACL on resource without authorization.
• 401.4 - Authorization failed by filter.
• 401.5 - ISAPI / CGI application authorization failure.
• 401.7 - Access denied URL authorization policy on the Web server. This error code is specific to IIS 6.0.
• 403 - Forbidden: IIS defines a number of different 403 errors that indicate a more specific cause of the error: • 403.1 - Execute access forbidden.
• 403.2 - Read access forbidden.
• 403.3 - Write access forbidden.
• 403.4 - requires SSL.
• 403.5 - requires SSL 128.
• 403.6 - IP address rejected.
• 403.7 - Client certificate required.
• 403.8 - Site access denied.
• 403.9 - Too many users number.
• 403.10 - configuration is invalid.
• 403.11 - password change.
• 403.12 - Access Denied Map.
• 403.13 - Client certificate revoked.
• 403.14 - Directory Listing Denied.
• 403.15 - Client Access Licenses exceeded.
• 403.16 - Client certificate is untrusted or invalid.
• 403.17 - Client certificate has expired or is not yet valid.
• 403.18 - Can not execute requested in the current application pool URL. This error code is specific to IIS 6.0.
• 403.19 - not execute CGI applications for the client in this pool. This error code is specific to IIS 6.0.
• 403.20 - Passport logon failed. This error code is specific to IIS 6.0.
• 404 - Not Found. • 404.0 - (None) - File or directory not found.
• 404.1 - Web site not accessible on the requested port.
• 404.2 - Web service extension lockdown policy prevents this request.
• 404.3 - MIME map policy prevents this request.
• 405 - used to access this page HTTP verb is not allowed (method not allowed.)
• 406 - Client browser does not accept the MIME type of the requested page.
• 407 - Proxy authentication required.
• 412 - Precondition failed.
• 413 - Request entity too large.
• 414 - Request-URI is too long.
• 415 - Unsupported media type.
• 416 - Requested range can not be met.
• 417 - Execution failed.
• 423 - Locked error.
5xx - Server Error
Since the server encountered an error and could not complete the request. • 500 - Internal server error. • 500.12 - Application is busy restarting on the Web server.
• 500.13 - Web server is too busy.
• 500.15 - does not allow direct request Global.asa.
• 500.16 - UNC authorization credentials incorrect. This error code is specific to IIS 6.0.
• 500.18 - URL authorization store can not be opened. This error code is specific to IIS 6.0.
• 500.100 - Internal ASP error.
• 501 - Header values specify a configuration that is not implemented.
• 502 - Web server received an invalid response while acting as a gateway or proxy server. • 502.1 - CGI application timeout.
• 502.2 - CGI application error. application.
• 503 - Service unavailable. This error code is specific to IIS 6.0.
• 504 - Gateway timeout.
• 505 - HTTP version not supported.
Common HTTP Status Codes and Their Causes
• 200 - Success. This status code indicates that IIS has successfully processed the request.
• 304 - Not Modified. The client requests a document already in its cache, the cache since the document has not been modified. The client uses the cached copy of the document, rather than downloading the document from the server.
• 401.1 - Logon failed. Login attempt is unsuccessful, probably because of a user name or password is invalid.
• 401.3 - due to ACL on resource without authorization. This means that the problem with NTFS permissions. Even if you have the appropriate permissions are trying to access files, this error may also occur. For example, if the IUSR account does not have access to C: WinntSystem32Inetsrv directory, you will see this error. For additional information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
187506 INFO: IIS 4.0 basis NTFS permissions of
• 403.1 - Execute access forbidden. The following are two common causes leading to this error message: • You do not have enough Execute permissions. For example, if the directory permissions are trying to access the ASP page is set to "no", or an attempt to execute CGI scripts directory permissions where is "only allows script", the error message will appear. To modify the Execute permissions, Management Console (MMC) Right-click the directory in Microsoft, and then click Properties and the Directory tab, make sure to set the appropriate permissions to execute trying to access the content.
• You will not attempt to execute the script file types mapped to verb (for example, GET or POST) used to identify. To verify this, right-click the directory in the MMC, click Properties, click the Directory tab and configure, and then verify that the appropriate file type script mapping is set up to allow the use of the verb.
• 403.2 - Read access forbidden. Verify that IIS is set to allow read access to the directory. 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 following article number to view the article in the Microsoft Knowledge Base:
247677 Error Message: 403.2 Forbidden: Read Access Forbidden ( 403.2 Forbidden: Read Access Forbidden)
• 403.3 - Write access is prohibited. Verify that the IIS permissions and NTFS permissions are set up in order to grant write access to the directory. For additional information about how to resolve this issue, 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 Forbidden: Write access forbidden)
• 403.4 - Requirements SSL. Disable the Require secure channel option, or use HTTPS instead of HTTP to access the page. If you do not install the certificate of the Web site this error, click the following article number to view the article in the Microsoft Knowledge Base:
224389 Error Message: HTTP Error 403,403.4,403.5 Forbidden: requires SSL
• 403.5 - SSL 128 required . Disable the Require 128-bit encryption option, or use 128-bit encryption browser to view the page. If you do not install the certificate of the Web site this error, click the following article number to view the article in the Microsoft Knowledge Base:
224389 Error Message: HTTP Error 403,403.4,403.5 Forbidden: SSL requirements
• 403.6 - IP address rejected. You have just your server is configured to deny access to your current IP address. For additional information about how to resolve this issue, 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 - Not available: IP address rejected)
• 403.7 - client certificate required. You have just your server is configured to require client authentication certificate, but you do not have a valid client certificate installed. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
190004 Error 403.7 or "Connection to Server Could Not Be Established " ( not establish a connection to the server)
186812 PRB: Error Message: 403.7 Forbidden : client certificate required (403.7 Forbidden: client certificate required)
• 403.8 - site access denied. You have your domain to access the server's domain name set limit. For additional information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
248032 Error Message: Forbidden: Site Access Denied 403.8 (Forbidden: Site Access Denied 403.8)
• 403.9 - User too many. The number of users connected to the server exceeds the connection limit that you set. For additional information about how to change this limit, click the following article number to view the article in the Microsoft Knowledge Base:
248 074 Error Message: Access Forbidden: Too Many Users Are Connected 403.9 ( Forbidden: Too many connected users 403.9)
Note: Microsoft Windows 2000 Professional and Microsoft Windows XP Professional automatically sets a limit on IIS up to 10 connections. You can not change this limit.
• 403.12 - Access Denied Map. The page you want to access requires a client certificate, but mapped to your client certificate user ID has been denied access to the file. For additional 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 - Forbidden: Access Denied Map)
• 404 - Not found. This error occurs because you try to access the file has been moved or deleted. If after installing URLScan tool, trying to access files with a limited extension, this error will occur. In this case, the word "Rejected by URLScan" in the log file entry of the request appear.
• 500 - Internal server error. Many server side error may result in the error message. Event Viewer log contains more detailed error reasons. In addition, you can disable friendly HTTP error messages to receive a detailed description of the error. For additional information about how to disable friendly HTTP error messages, click the following article number to view the article in the Microsoft Knowledge Base:
294807 How to disable Internet Explorer "Show Friendly HTTP Error Messages" feature on the server side of 5
• 500.12 - Application is restarting. This means that you restart the application process in IIS tries to load the ASP page. After refreshing the page, this message will disappear. If you refresh the page, this message appears again, it may be anti-virus software is scanning the Global.asa file. For additional 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 you try to load an ASP page that contains the error code, this error message will appear. To get a more exact error message, disable friendly HTTP error messages. By default, this error message will only be enabled on the default Web site. For additional information about how to see 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, without displaying 500-100. asp ASP error message
• 502 - gateway error. If you try to run a CGI script that does not return a valid set of HTTP headers, this error message will appear.
The FTP
1xx - Positive Preliminary reply
These status code indicates that an action has started successfully, but the client wants to get another reply before proceeding new command. • 110 Restart marker reply.
• 120 Service ready in nnn minutes.
• 125 Data connection open, transfer starting.
• 150 File status okay, about to open data connection.
2xx - Positive Completion reply
An action has been completed successfully. The client can execute a new command. • 200 Command OK.
• 202 Command not implemented, 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 an official system name listed in the Assigned Numbers document.
• 220 Service ready for new user requests.
• 221 Service closing control connection. If appropriate, please log out.
• 225 Data connection open, transfer is not in progress.
• 226 Closing data connection. Requested file operation was successful (e.g., transfer or file abort).
• 227 enters passive mode (h1, h2, h3, h4 , p1, p2).
• 230 User logged in, proceed.
• 250 Requested file correct operation has been completed.
• 257 have been created "PATHNAME".
3xx - Positive Intermediate reply
The command was successful, but the server needs additional information from the client to complete processing the request. • 331 User name okay, need password.
• 332 Need account for login.
• 350 Requested file action pending further information.
4xx - Transient Negative Completion Reply
This command is not successful, but the error is temporary. If the client retries the command, it may succeed. • 421 Service not available, closing control connection. If the service determines that it must shut down, it sends the response to any command.
• 425 Can not open data connection.
Closed Connection 426 •;. Transfer aborted
• 450 requested action not file. File unavailable (eg, file busy).
• 451 requested action aborted: local error in processing.
• 452 Requested action not executed. Insufficient system memory.
5xx - Permanent Negative Completion Reply
This command is not successful, the error is permanent. If the client retries the command, the same error occurs again. • 500 Syntax error, command is not recognized. This may include errors such as command line too long and the like.
• 501 Syntax error in the parameters.
• 502 Command not implemented.
• 503 Bad sequence of commands.
• 504 Command parameter not implemented.
• 530 logged in.
• 532 Need account for storing files.
• 550 requested operation is not performed. File unavailable (eg, file not found, no access).
• 551 requested action aborted: Page type unknown.
• 552 requested file operation terminates abnormally: Exceeded storage allocation (or data set to the current directory).
• 553 Requested action not executed. File name not allowed.
Common FTP Status Codes and Their Causes
• 150 - FTP uses two ports: 21 for sending commands, 20 for sending data. Status code 150 indicates that the server opens a new connection on port 20, send some data.
• 226 - command opens a data connection to perform an operation, such as transferring files on port 20. This operation completed successfully, the data connection is closed.
• 230 - After the client sends the correct password, displays the status code. It indicates that the user has successfully logged.
• 331 - after the client sends a user name, display the status code. Username Regardless of whether the system provides a valid account, it will show the status code.
• 426 - command opens a data connection to perform an operation, but the operation has been canceled, the data connection is closed.
• 530 - This status code indicates that the user can not log on because the user name and password combination is not valid. If you use a user login account, you may type the wrong user name or password, or may choose to only allow anonymous access. If you log in using the anonymous account, IIS configuration may refuse anonymous access.
• 550 - The command is not executed because the specified file is not available. For example, to GET the file does not exist, or trying to PUT the file you do not have write permissions to the directory.
Reproduced in: https: //www.cnblogs.com/Codenewbie/p/3445584.html