HTTP Errors

From Wiki
Jump to: navigation, search

HTTP Error Codes

This is a list of the most common Hypertext Transfer Protocol (HTTP) status codes that you may come across as errors while working on your site. These codes are internet standards and are problem specific. However, some errors are given off as a general response and may not actually be related to root cause of the problem.

Note: This wiki does not list every possible HTTP status code as dictated in the HTTP specification nor does it cover custom Internet Server API (ISAPI) filters or a custom HTTP modules that have set their own HTTP status codes.

4xx - Client Error

400 level HTTP status codes will happen when an error occurs on the client browsers, or it appears to be a fault. The client browser may have requested a page that does not exist because of a misspelling or the actual folder/file are missing. The client browser also may not have proper permissions to view the content on that web page.

Here is a list of common IIS 7.0 4xx errors:

400 - Bad request

The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.

       400.1 - Invalid Destination Header.
       400.2 - Invalid Depth Header.
       400.3 - Invalid If Header.
       400.4 - Invalid Overwrite Header.
       400.5 - Invalid Translate Header.
       400.6 - Invalid Request Body.
       400.7 - Invalid Content Length.
       400.8 - Invalid Timeout.

401 - Access denied

       401.1 - Logon failed.
       401.2 - Logon failed due to server configuration.
       401.3 - Unauthorized due to ACL on resource.
       401.4 - Authorization failed by filter.
       401.5 - Authorization failed by ISAPI/CGI application.

Solutions to 401 errors

This usually indicated that you probably have the wrong log-in information. Verify you have the correct information. If you continue to have issues, you may need to reset your password from the client billing area, or request that support resets your password for you.

403 - Forbidden

403 Forbidden errors are the most common client errors.

       403.1  - Execute access forbidden.
       403.2  - Read access forbidden.
       403.3  - Write access forbidden.
       403.4  - SSL required.
       403.5  - SSL 128 required.
       403.6  - IP address rejected.
       403.7  - Client certificate required.
       403.8  - Site access denied.
       403.9  - Forbidden: Too many clients are trying to connect to the Web server.
       403.10 - Forbidden: Web server is configured to deny Execute access.
       403.11 - Forbidden: Password has been changed.
       403.12 - Mapper denied access.
       403.13 - Client certificate revoked.
       403.14 - Directory listing denied.
       403.15 - Forbidden: Client access licenses have exceeded limits on the Web server.
       403.16 - Client certificate is untrusted or invalid.
       403.17 - Client certificate has expired or is not yet valid.
       403.18 - Cannot execute requested URL in the current application pool.
       403.19 - Cannot execute CGI applications for the client in this application pool.
       403.20 - Forbidden: Passport logon failed.
       403.21 - Forbidden: Source access denied.
       403.22 - Forbidden: Infinite depth is denied.
       403.502 - Forbidden: Too many requests from the same client IP; Dynamic IP Restriction limit reached.

cPanel solutions to 403 errors

  1. Log into your cPanel
  2. Go to File Manager (Selecting the public_html folder to access in the pop-up)
  3. Navigate to the file or folder you are trying to access and highlight that folder/file
  4. At the top there is a set of controls, select Change Permissions (Note: The most common setting is 755)

WCP solutions to 403 errors

Currently, a request will need to be made at or emailing us at [email protected] to change/check the permission levels for the folder/file you are trying to access.

404 - Not found

The second most common client error is the 404 Not Found error.

       404.0  - Not found.
       404.1  - Site Not Found.
       404.2  - ISAPI or CGI restriction.
       404.3  - MIME type restriction.
       404.4  - No handler configured.
       404.5  - Denied by request filtering configuration.
       404.6  - Verb denied.
       404.7  - File extension denied.
       404.8  - Hidden namespace.
       404.9  - File attribute hidden.
       404.10 - Request header too long.
       404.11 - Request contains double escape sequence.
       404.12 - Request contains high-bit characters.
       404.13 - Content length too large.
       404.14 - Request URL too long.
       404.15 - Query string too long.
       404.16 - DAV request sent to the static file handler.
       404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.
       404.18 - Querystring sequence denied.
       404.19 - Denied by filtering rule.
       404.20 - Too Many URL Segments

5xx - Server Errors

Here a couple of common 5xx server errors you may come across. Any 500 level errors need to be handled by our support staff. You can notify support at [email protected] or visiting

500 - Internal Server Error

       500.0  - Module or ISAPI error occurred.
       500.11 - Application is shutting down on the Web server.
       500.12 - Application is busy restarting on the Web server.
       500.13 - Web server is too busy.
       500.15 - Direct requests for Global.asax are not allowed.
       500.19 - Configuration data is invalid.
       500.21 - Module not recognized.


Header values specify a configuration that is not implemented.


Web server received an invalid response while acting as a gateway or proxy.

       502.1 - CGI application timeout.
       502.2 - Bad gateway.

503 - Service Unavailable

       503.0 - Application pool unavailable.
       503.2 - Concurrent request limit exceeded.

For more information please reference:

Internet Standards