HTTP Error Codes

Server error code Daquan

• 400-bad Request.

• 401-access is Denied. IIS defines a number of different 401 errors, which indicate a more specific cause of the Error. These specific error codes are displayed in the browser but are not displayed in the IIS log: • 401.1-login Failed.

• 401.2-server configuration causes logon Failures.

• 401.3-not authorized due to ACL restrictions on Resources.

• 401.4-filter Authorization Failed.

401.5-ISAPI/CGI Application Authorization Failed.

401.7– access is denied by the 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-execution access is Forbidden.

• 403.2-read access is Forbidden.

• 403.3-write access is Forbidden.

• 403.4-requires SSL.

• 403.5-requires SSL 128.

The 403.6-IP address is Rejected.

• 403.7-requires a client Certificate.

• 403.8-site access is Denied.

• 403.9-excessive number of Users.

• 403.10-invalid Configuration.

• 403.11-password Change.

• 403.12-deny access to the mapping Table.

• 403.13-the client certificate is Revoked.

• 403.14-reject directory List.

• 403.15-client access Permission Exceeded.

• 403.16-client certificate is not trusted or invalid.

• 403.17-the client certificate has expired or is not yet valid.

• 403.18-the requested URL cannot be executed in the current application Pool. This error code is specific to IIS 6.0.

• 403.19-CGI cannot be executed for clients in this application Pool. This error code is specific to IIS 6.0.

403.20-passport Login Failed. This error code is specific to IIS 6.0.

• 404-not found. • 404.0-(none) – No files or directories found.

• 404.1-unable to 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.

• 405-the HTTP verb used to access this page is not allowed (method not allowed)

• 406-the client browser does not accept the MIME type of the requested Page.

• 407-proxy authentication is Required.

• 412-precondition Failed.

413– request entity is too large.

• 414-the request URI is too long.

415– Media Types not Supported.

The range requested by 416– is not sufficient.

417– Execution Failed.

423– a locked Error.

Continue the initial request has been accepted and the customer should continue to send the remainder of the Request. (HTTP 1.1 New)

The 101 switching protocols server translates the Client's request to another protocol (HTTP 1.1 new

All ok, the answer document for Get and post requests is Followed.

The 201 Created server has created the document, and the location header gives its url.

202 Accepted has accepted the request, but the processing has not been completed.

203 Non-authoritative Information The document has returned normally, but some of the answer headers may be incorrect because a copy of the document (HTTP 1.1 New) is being used.

204 No Content There is no new document, the browser should

Continue to display the original Document.

205 Reset content is not new, but the browser should reset what it displays. Used to force the browser to clear the form input (HTTP 1.1 new).

The 206 Partial Content client sends a GET request with a range header that the server has completed (HTTP 1.1 new).

Multiple Choices customer requested documents can be found in multiple locations that have been listed in the returned Document. If the server wants to make a preference, it should be indicated in the location answer Header.

301 Moved Permanently The document requested by the customer elsewhere, the new URL is given in the location header, and the browser should automatically access the new Url.

302 Found is similar to 301, but the new URL should be treated as a temporary replacement, not a Permanent. Note that the corresponding status information in HTTP1.0 is "Moved temporatily", and when the status code appears, the browser can automatically access the new url, so it is a useful status Code. Note that this status code can sometimes be used with 301 Substitutions. For example, if the browser mistakenly requests Http://host/~user (the trailing slash is missing), some servers return 301, and some return 302. Strictly speaking, We can only assume that the browser will automatically redirect only if the original request is Get. See 307.

303 See other is similar to 301/302, except that if the original request is the Post,location header the specified redirect target document should be fetched via get (HTTP 1.1 new).

304 Not Modified client has buffered documents and issued a conditional request (typically providing a if-modified-since header indicating that the customer only wants to update the document than the specified date). The server tells the customer that the original buffered document can continue to be used.

305 Use proxy The document requested by the client should be extracted from the agent server indicated by the location header (HTTP 1.1 is new).

307 temporary Redirect and 302 (Found) are the Same. Many browsers incorrectly respond to a 302 response for redirection, even if the original request is post, even though it can actually be redirected only if the answer to the POST request is 303. For this reason, HTTP 1.1 has been added in 307 to allow for more cleanup of the region in several status codes: when a 303 response occurs, the browser can follow the redirected get and post requests, and if the 307 answer, the browser can only follow the redirect to the Get Request. (HTTP 1.1 New)

A syntax error has occurred in the request Requests.

401 Unauthorized customer attempts to access password-protected pages without Authorization. A www-authenticate header is included in the answer, and the browser displays the user Name/password dialog box, and then makes a request again after filling in the appropriate authorization Header.

403 Forbidden resource is not available. The server understands the Customer's request, but refuses to process it. This is usually caused by the permissions set on the file or directory on the Server.

404 Not Found Could not find the resource at the specified Location. This is also a common answer,

The 405 method not allowed request methods (GET, POST, HEAD, DELETE, PUT, trace, etc.) do not apply to the specified resource. (HTTP 1.1 New)

406 not acceptable the specified resource has been found, but it's MIME type and the client is in the Accpet header

Incompatible (HTTP 1.1 New) specified in The.

HTTP 400-invalid Request

HTTP 401.1-unauthorized: Logon failed

HTTP 401.2-unauthorized: Server configuration issues cause logon failure

HTTP 401.3-acl prohibit access to resources

HTTP 401.4-unauthorized: authorization denied by filter

HTTP 401.5-unauthorized: ISAPI or CGI authorization failed

HTTP 403-no Access

HTTP 403-access to Internet Service Manager (HTML) 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-no access: SSL required

HTTP 403.5-no access: 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-no access: Too many users connected

HTTP 403.10-no access: Invalid configuration

HTTP 403.11-no access: Password Change

HTTP 403.12-no access: Mapper denied access

HTTP 403.13-no access: Client certificate has been revoked

HTTP 403.15-no access: Too many client access licenses

HTTP 403.16-forbidden: client certificate is untrusted or invalid

HTTP 403.17-forbidden: client certificate has expired or is not yet valid

HTTP 404.1-unable to find Web site

HTTP 404-file not found

HTTP 405-resource is forbidden

HTTP 406-unacceptable

HTTP 407-proxy Authentication Required

HTTP 410-never Available

HTTP 412-prerequisite Failure

HTTP 414-request-URI too long

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

HTTP 500-14-application Not valid

HTTP 500-15-request Global.asa not allowed

Error 501-not implemented

HTTP 502-gateway Error

HTTP Error Codes