HTTP Error Codes

Common HTTP status codes and their causes

-Success. This status code indicates that the request was successfully processed by IIS.

304 -not modified. The document requested by the client is already in its cache and the document has not been modified since it was cached. The client uses a cached copy of the document instead of downloading the file from the server.

401 -Login failed. The logon attempt was unsuccessful, possibly because the user name or password is invalid.

403.1 -execution access is forbidden. The following are the two common causes of this error message: You do not have sufficient permission to execute.

403.2 -Read access is forbidden. Error message: 403.2 forbidden:read access Forbidden (403.2 Forbidden: Read access Forbidden)

403.3 -Write access is forbidden. Error message: 403.3 forbidden:write access Forbidden (403.3 Forbidden: Write access Forbidden)

403.4 -Requires SSL. Error message: HTTP error 403, 403.4, 403.5 Forbidden: SSL Required

403.5 -requires SSL 128. Error message: HTTP error 403, 403.4, 403.5 Forbidden: SSL Required

403.6 -The IP address is denied. You have configured your 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 article in the Microsoft Knowledge Base:

248043 error message: 403.6-FORBIDDEN:IP address rejected (403.6-unavailable: IP address denied)

403.7 -Requires a client certificate. You have configured your server to require a client authentication certificate, but you do not have a valid client certificate installed. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

190004 error 403.7 or "Connection to server Could not being established" (unable to establish a connection to the server)

186812 PRB: Error message: 403.7 forbidden:client Certificate Required (403.7 Forbidden: Require client certificate)

403.8 -site access is denied. You have set a domain name limit for the domain that you use to access the server. For additional information about how to resolve this issue, click the article number below 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 -Excessive number of users. 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:

248074 error message: Access Forbidden:too Many users are Connected 403.9 (forbidden: Too many users connected 403.9)

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

403.12 -denied access to the mapping table. The page you want to access requires a client certificate, but the user ID that is mapped to your client certificate 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: Mapping table denied access)

404 -not found. This error occurs because the file that you are trying to access has been moved or deleted. This error can also occur if you try to access a file with a limited extension after you install the URLScan tool. In this case, the word "Rejected by URLScan" appears in the log file entry for the request.

-Internal server error. Many server-side errors can cause this error message. The Event Viewer log contains a more detailed cause of the error. Additionally, you can disable friendly HTTP error messages in order to receive detailed error descriptions. 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 the "show friendly HTTP error Messages" feature on the server side of Internet Explorer 5

500.12 -the application is restarting. This indicates that you attempted to load an ASP page during IIS restart of the application. When the page is refreshed, this information disappears. If this information appears again after the page is refreshed, the antivirus software may be 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 500-12 application is restarting)

500-100.asp-asp error. This error message appears if you try to load an ASP page that contains an error code. To obtain a more accurate error message, disable the friendly HTTP error message. By default, this error message is only 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 displays an HTTP 500 error message without displaying the ASP error message for 500-100.asp

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

Ftp

1xx -Affirmative initial reply

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

A. Restart tag reply.

The service is ready and starts in nnn minutes.

The data connection is open and the transfer is starting.

The file status is normal and you are ready to open the data connection.

2xx -sure to complete the reply

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

The order is determined.

202 Command 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.

215 Name System type, where name is the formal system name listed in the Assigned Numbers document.

The service is ready to execute the request of the new user.

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

The 225 data connection is open and there are no in-progress transmissions.

226 Close the data connection. The requested file operation was successful (for example, transferring a file or discarding a file).

227 into passive mode (H1,H2,H3,H4,P1,P2).

User is logged in and continues.

The requested file operation is correct and completed.

257 has created "PATHNAME".

3xx -Affirmative intermediate reply the command was successful, but the server needed more information from the client to complete the processing of the request.

331 User name is correct and requires a password.

332 requires a login account.

The requested file operation is waiting for further information.

4xx -complete reply for transient negation

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

The 421 service is not available and is shutting down the control connection. If the service determines that it must be closed, this response is sent to any command.

425 cannot open the data connection.

426 Connection closed; Transfer aborted.

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

451 requested operation aborted: Local error is being processed.

452 The requested operation was not performed. The system does not have enough storage space.

5xx -Permanent negation of complete reply

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

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

501 has syntax errors in the arguments.

502 Command not executed.

503 the wrong command sequence.

504 The command that did not execute the parameter.

530 is not logged in.

532 The storage file requires an account.

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

551 requested operation aborted: unknown page type.

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

553 The requested operation was not performed. The file name is not allowed.

Common FTP status codes and their causes

Four-FTP uses two ports: 21 for sending commands, and 20 for sending data. 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 is closed.

When the client sends the correct password, the status code is displayed. It indicates that the user has successfully logged on.

331 -The status code is displayed after the client sends the user name. The status code is displayed regardless of whether the provided 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 is closed.

530 -The status code indicates that the user cannot log on because the user name and password combination is not valid. If you are logged on with a user account, you might type an incorrect user name or password, or you may choose to allow only anonymous access. If you log on with 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 into a directory where you do not have write permission.

This article is from the "Liew" blog, make sure to keep this source http://walterliew.blog.51cto.com/11286797/1883907

HTTP Error Codes