subject: Web Server Error Codes: Client Error [print this page] In the last article I had mentioned about the Web Server Error Code which gives the status of your request. Now in this article I will let you know about the Web sever error code which will indicate the error caused by user while requesting to the Web Server. Generally by mistake the user has done something which will give rise to these errors. These are the following Error codes which come in this category:
4XX Client Error:
400 Bad Request: This code indicates that there is a syntax error while writing the URL.
401 Unauthorized: This code indicates that user request for a specific URL cant be fulfilled because the authentication WWW - Authenticate header file for a particular resource is required and has not yet been provided.
402 Payment Required: This error code indicates that this code might be used as part of some form of cash transfer scheme, but that has not happened.
403 Forbidden: This code indicates that request from user was a valid request, but the server is refusing to respond to it. Unlike a 401 unauthorized response authentication is approved but the credentials still do not grant the user permission to access the resource.
404 Not Found: This error code indicate that the requested page could not be found but may be available again in the future.
405 Method Not Allowed: This error code indicate that the resource cant be accessed by using the current requesting method.
406 Not Acceptable: This error code indicates that error the response of accessed source is unacceptable to the user.
407 Proxy Authentication Required: The user must first authenticate itself with the proxy.
408 Request Timeout: This code indicates that server timeout waiting for the request from the user.
409 Conflict: This code indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
410 Gone: This error code indicates that requested source is no longer available.
411 Length Required: The code shows that request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed: The precondition given in the request does not meet the one accepted by the resource.
413 Request Entity Too Large: The server is unable to accept the request because the request entity is too large.
414 Request-URI Too Long: The universal resource identifiers provided was too long for the server to process.
415 Unsupported Media Type: This code indicates that user request entity contain media type not supported by the resource.
416 Requested Range Not Satisfiable: The user has requested for particular portion of file but resource is unable to provide it.
417 Expectation Failed: The server cant provide the result according to the request made by the user.
422 Unprocessable Entity: The request of user is not fulfilled because it contains semantic error.
423 Locked: The resource that user has requested is locked.
424 Failed Dependency: The request failed due to failure in previous request.
425 Unordered Collection: The resource requested by user is not according to the Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol.
426 Upgrade Required: The client should switch to a different protocol.
429 Too Many Requests: The user has sent too many requests in a given amount of time.
431 Request Header Fields Too Large: The server is unable to process the request because the individual header file size or collective header file size is too large.
444 No Response: This error code indicates that server has returned no information to the client and closed the connection. It is also useful as a deterrent for malware.
495 Cert Error: This error code is generated when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection.
496 No Cert: This error code is generated when user didn't provide certificate to distinguish it from 4XX in a log and an error page redirection.
497 HTTP to HTTPS: This error code is used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection.
499 Client Closed Request: This error code is generated when the connection has been closed by user while the server is still processing its request, making server unable to send a status code back.
Thus by having knowledge of above mentioned error code you can make changes in your attempt to request for the desired services. By these you can do online troubleshooting without any help of computer expert.
