When a client uses an HTTP data stream to transfer a URL resource to the server, it may need to specify the media type that is being transferred. This error will be generated if any of the following criteria are met: If the specified media type does not match the […]
414: Request URI Too Long
A 414 error page requires that you use a URL formed in a way that successfully reaches a server and is too long for the server to process based on its restrictions. Due to both of these needing to be true, this error is rarely generated. If you experience this […]
413: Request Entity Too Long
When the HTTP data stream sent by the client to the server is too large, the server will generate this error page. What is or is not “too large” depends on the client’s request and restrictions placed on the server. This issue would require ensuring that the correct method to […]
412: Precondition Failed
An HTTP client using an HTTP data stream to send data to the server can include specifications for the stream, known as Preconditions. If a precondition were specified but not met, the server would generate this error page. This issue may only be generated when a client-side application does not meet the specifications […]
411: Content-Length Required
When using HTTP methods that involve placing data on a server, such as PUT or POST, the server may require the length of the data to be specified. If the length must be specified and the request fails, this error page will be returned. This issue will require restructuring the […]
410: Gone
Sometimes a server can provide a 410 error page instead of a 404 error. These error pages are fundamentally the same, indicating that a resource that has been requested is not available. However, the 410 error page code provides the additional information that the resource previously existed but is no […]
409: Conflicting Request
When the request you have made conflicts with an established rule, the server may generate a 409 error page to indicate two requests that conflict with each other. This issue is rarely caused by standard Web server authority or security as those processes will generate different errors. A 409 error […]
408: Request Timed Out
This error page is caused when the servers drop the connection to your client because too much time has passed between the initial connection being established and data transmission. Many potential issues can cause this problem, including load on the client matching, issues with your local area network, issues with […]
407: Proxy Authentication Required
This error page is an issue with authentication, similar to a 401 error page. The difference is mainly in how the server requires authentication. While a server generating a 401 error requires direct authentication, a 407 error would be generated by a server configured to require authentication via a proxy.
406: Not Acceptable
When requesting information from the server, the browser or client also includes a specification requesting the format it wants the information returned. If the server cannot accommodate this request, it will return a 406 Not Acceptable error page. This error infrequently occurs in Web browsers because most browsers will accept any data […]