Comprehensive List of HTTP Status and Error Codes

During your HTTP sessions, you'll receive various numbered codes from Web servers. When connected via HTTP, CuteFTP displays these codes in the log window. Some codes represent errors. Most others simply communicate the status of the connection. Here are brief explanations for the most common status and error codes.

100 200 300 400 500

Series Series Series Series Series Description

Error or Status Code

100 Informational - These status codes indicate a provisional response. Series The client should be prepared to receive one or more 1xx responses before receiving a regular response. 100 101 Continue. Switching protocols. Description 200 Success - This class of status codes indicates that the server Series successfully accepted the client request. 200 201 202 203 204 205 206 Okay - The client request has succeeded This status code indicates that the Web server has successfully processed the request Created. Accepted. Non-authoritative information. No content. Reset content. Partial content.

207

Multi-Status (WebDAV)The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

300 Redirection - The client browser must take more action to fulfill the Series request. For example, the browser may have to request a different page on the server or repeat the request by using a proxy server. 302 304 Object moved. Not modified. The client requests a document that is already in its cache and the document has not been modified since it was cached. The client uses the cached copy of the document, instead of downloading it from the server Temporary redirect.

307

400 Client Error - An error occurs, and the client appears to be at fault. Series For example, the client may request a page that does not exist, or the client may not provide valid authentication information. 400 401 Bad request. Access denied.

401.1 Logon failed. The logon attempt is unsuccessful, probably because of a user name or password that is not valid. 401.2 Logon failed due to server configuration. 401.3 Unauthorized due to ACL on resource. This indicates a problem with NTFS permissions. This error may occur even if the permissions are correct for the file that you are trying to access. For example, you see this error if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory. 401.4 Authorization failed by filter. 401.5 Authorization failed by ISAPI/CGI application. 401.7 403 Access denied by URL authorization policy on the Web server. This error code is specific to IIS 6.0. Forbidden.

403.1 Execute access forbidden. The following are two common causes of this error message:

You do not have enough Execute permissions. For example, you may receive this error message if you try to access an ASP page in a directory where permissions are set to None, or you try to execute a CGI script in a directory with Scripts Only permissions. The script mapping for the file type that you are trying to execute is not set up to recognize the verb that you are using (for example, GET or POST).

403.2

Read access forbidden. Verify that you have Read access to the directory. Also, if you are using a default document, verify that the document exists.

403.3 Write access forbidden. Verify that you have Write access to the directory 403.4 SSL required. Use HTTPS instead of HTTP to access the page. 403.5 SSL 128 required. 403.6 IP address rejected. 403.7 Client certificate required. You do not have a valid client certificate installed 403.8 Site access denied. 403.9 Too many users. The number of users who are connected to the server exceeds the connection limit.

403.1 Invalid configuration. 0 403.1 Password change. 1 Mapper denied access. The page that you want to access requires a client 403.1 certificate, but the user ID that is mapped to your client certificate has been 2 denied access to the file. 403.1 Client certificate revoked. 3 403.1 Directory listing denied. 4 403.1 Client Access Licenses exceeded. 5 403.1 Client certificate is untrusted or invalid. 6

403.1 Client certificate has expired or is not yet valid. 7 403.1 Cannot execute requested URL in the current application pool. This error code 8 is specific to IIS 6.0. 403.1 Cannot execute CGIs for the client in this application pool. This error code is 9 specific to IIS 6.0. 403.2 Passport logon failed. This error code is specific to IIS 6.0. 0 404 Not found. This error may occur if the file that you are trying to access has been moved or deleted.

404.0 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 406 407 412 413 414 415 416 417 423 424 425 426 449 HTTP verb used to access this page is not allowed (method not allowed). Client browser does not accept the MIME type of the requested page. Proxy authentication required. Precondition failed. Request entity too large. Request-URL too long. Unsupported media type. Requested range not satisfiable. Execution failed. Locked error. Failed Dependency. The request failed due to failure of a previous request Unordered Collection Upgrade Required. The client should switch to transport layer security. Retry With A Microsoft extension: The request should be retried after doing the appropriate action.

500 Server Error - The server cannot complete the request because it Series encounters an error. 500 Internal server error. You see this error message for a wide variety of serverside errors.

500.1 Application is busy restarting on the Web server. Indicates that you tried to 2 load an ASP page while IIS was in the process of restarting the application. This message should disappear when you refresh the page. If you refresh the page and the message appears again, it may be caused by antivirus software that is scanning your Global.asa file. 500.1 Web server is too busy. 3 500.1 Direct requests for Global.asa are not allowed. 5 500.1 UNC authorization credentials incorrect. This error code is specific to IIS 6.0. 6 500.1 URL authorization store cannot be opened. This error code is specific to IIS 8 6.0. 500.1 Internal ASP error. You receive this error message when you try to load an 00 ASP page that has errors in the code. 501 502 Header values specify a configuration that is not implemented. Bad Gateway. Web server received an invalid response while acting as a gateway or proxy. You receive this error message when you try to run a CGI script that does not return a valid set of HTTP headers.

502.1 CGI application timeout. 502.2 Error in CGI application. 503 504 505 506 507 Service unavailable. This error code is specific to IIS 6.0. Gateway timeout. HTTP version not supported. Variant Also Negotiates Insufficient Storage

509 510

Bandwidth Limit Exceeded This status code, while used by many servers, is not an official HTTP status code Not Extended