HTTP status Code Daquan (200, 404, 500, etc.)

Invalid HTTP 400– request
HTTP 401.1– not authorized: Logon failed
HTTP 401.2– not authorized: Login failed due to server configuration problem
HTTP 401.3–acl prohibit access to resources
HTTP 401.4– not authorized: Authorization denied by filter
HTTP 401.5– not authorized: ISAPI or CGI authorization failed
HTTP 403– Disable Access
HTTP 403– access to Internet Service Manager is limited to Localhost
HTTP 403.1 Forbidden: Disable executable access
HTTP 403.2– Forbidden: Disable Read access
HTTP 403.3– Forbidden: write-Access Forbidden
HTTP 403.4– Forbidden: SSL Required
HTTP 403.5– Forbidden: SSL 128 Required
HTTP 403.6– Forbidden: IP address denied
HTTP 403.7– Forbidden: Require client certificate
HTTP 403.8– Forbidden: Prohibit site access
HTTP 403.9– Forbidden: Too many users are connected
HTTP 403.10– Forbidden: Invalid configuration
HTTP 403.11– Forbidden: Password change
HTTP 403.12– Forbidden: Mapper denied access
HTTP 403.13– Forbidden: Client certificate has been revoked
HTTP 403.15– Forbidden: Too many client access licenses
HTTP 403.16– Forbidden: Client certificate is untrusted or invalid
HTTP 403.17– Forbidden: Client certificate has expired or has not been effective HTTP 404.1-

HTTP 500– Internal Server error
HTTP 500.100– Internal Server error –asp error
HTTP 500-11 Server shutdown
HTTP 500-12 Application Restart
HTTP 500-13– Server Too busy
Invalid HTTP 500-14– application
HTTP 500-15– does not allow request Global.asa
Error 501– Not implemented
HTTP 502– Gateway Error

These status codes represent a temporary response. The client should be prepared to receive one or more 1xx responses before receiving a regular response. 100– continues.
101– switch protocol.
2xx– success

The client browser must take more action to implement the request. For example, the browser might have to request a different page on the server, or repeat the request through a proxy server.
The 302– object has been moved.
304– not modified.
307– temporary redirection.
4xx– Client Error

403– Forbidden: IIS defines a number of different 403 errors that indicate a more specific cause of the error:

404– not found. 404.0-(None) – No files or directories found.
404.1– cannot access the WEB site on the requested port.
The 404.2–web service extension lockout policy blocks this request.
The 404.3–mime mapping policy blocks this request.

The server could not complete the request because it encountered an error.
500– Internal server error.
The 500.12– application is busy restarting on the WEB server.
The 500.13–web server is too busy.
500.15– does not allow direct request for Global.asa.
500.16–unc authorization credentials are incorrect. This error code is specific to IIS 6.0.
The 500.18–url authorization store cannot be opened. This error code is specific to IIS 6.0.
500.100– Internal ASP error.

The 503– service is not available. This error code is specific to IIS 6.0.
The 504– gateway timed out.
505–http version is not supported.

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. For additional information about how to resolve this issue, click the article number below 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 forbidden. Verify that IIS permissions 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 article in the Microsoft Knowledge Base:
248072 error message: 403.3 forbidden:write access Forbidden (403.3 Forbidden: Write access Forbidden)
403.4– requires SSL. Disable the Require secure channel option, or use HTTPS instead of HTTP to access the page. If this error occurs on a Web site that does not have a certificate installed, 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 Required
403.5– requires SSL 128. Disable the Require 128-bit encryption option, or use a browser that supports 128-bit encryption to view the page. If this error occurs on a Web site that does not have a certificate installed, 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 Required
The 403.6–IP address is rejected. 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– not available: 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– too many 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.
500– 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.

These status codes indicate that an operation has started successfully, but the client wants to get another reply before continuing with the new command. 110 Restart Tag reply.
120 service is ready, starting in nnn minutes.
125 The data connection is open and the transfer is starting.
150 file status OK, ready to open data connection.
2xx– sure to complete the reply

The command was successful, but the server needs more information from the client to complete the processing of the request. 331 user name is correct, password required.
332 You need to log in to your account.
350 The requested file operation is waiting for further information.
4xx– Transient negation Completion reply

The command is unsuccessful, but the error is temporary. If the client retries the command, it may execute successfully.
421 service is not available and the control connection is shutting down. If the service determines that it must be closed, this response is sent to any command.
425 The data connection cannot be opened.
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 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

Common FTP status codes and their causes
The 150–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.
The 226– 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.
After the 230– client sends the correct password, the status code is displayed. It indicates that the user has successfully logged on.
The status code is displayed after the 331– client sends the user name. The status code is displayed regardless of whether the provided user name is a valid account in the system.
The 426– 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.
The 550– 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.

HTTP status Code Daquan (200, 404, 500, etc.)