A status code 400 or a three-digit code beginning with 4xx indicates a client error. When the client sends a request to the server that is damaged or faulty, the server issues a 400 status code. It is essential to correct 4xx errors on a website so that users can access all the content on the site.[1]
Background
A status code 400 or class 4xx is intended to draw attention to errors caused by client requests (bad request or bad request). To identify faulty access as precisely as possible, the server in question should issue the exact 4xx code in the event of a failed request.
List of all 4xx status codes
Errors with status code 400 are listed below:
- 400: All errors with the 4xx status code indicate a bad request.
- 401 unauthorized: This request to the server requires the client to authorize it. Usually this is done by logging in. If a user still wants to access the password-protected resource, the 401 (unauthorized) status code appears with a note on what to do.
- 402 payment required: This status code is not yet used. In the future, it will indicate that you must pay a fee to view the content and that it will only be visible after payment.
- 403 forbidden: This status code differs from a 401 error in that access is denied even with valid login details. This happens, for example, when a site is requested with HTTP, but it is configured with https.
- 404 not found: One of the most frequently displayed status codes is the 404 error. It is used to indicate that a requested link does not exist or no longer exists (dead link). If an error page displays a status code that differs from the 404 code, you get a "soft 404-error".
- 405 method not allowed: The request was made using the wrong method. The method that is required, such as GET, is explained by the solution within the error code.
- 406 not acceptable: For this case, the format requested by the client cannot be issued by the server. The content type is enabled in the server solution.
- 407 proxy authentication required: Similar to status code 401, the server requests authentication from the client. Here, however, in connection with the proxy server that is used.
- 405 request time-out: This code is shown if the client could not send a complete request in the period of time defined by the server.
- 409 conflict: This request by the client is rejected by the server because it was sent under a false assumption. This status code can go out if the resource has been modified.
- 410 gone: If the user receives this status code, it means that the resource is no longer enabled and / or has been deleted.
- 411 length required: If this code appears, you need to specify the length of the content in the header to process the client's request.
- 412 precondition failed: For this case, the precondition has been defined in the request, which is not valid.
- 413 request entity too large: This status code indicates that the request was too large to be processed by the server in question. The server solution may include an instruction to try again later.
- 414 request-url too long: The server cannot respond because the URL is too long. This is generally caused by too many deviations.
- 415 unsupported media type: Unable to respond to this request because the media type is not enabled.
- 416 request range not satisfiable: This error code indicates that a part of the requested resource is no longer enabled or is invalid.
- 417 expectation failed: This code will be issued if the "expect" field in the header specifies a particular request that the server cannot fulfill.
- 422 unprocessable entity: This code indicates that the request cannot be processed. This can be generated by semantic errors, but not by media type errors such as 415.
- 423 locked: This code means that the requested resource is temporarily blocked and is not reachable.
- 424 failed dependency: If this status code is issued, two requests are made. The second request depended on the first, but was unsuccessful.
- 426 upgrade required:: In order for the server to handle this request, the client must use TLS 1.0.
- 428 precondition required: For this request to be successful, several preconditions must have been met.
- 429 too many requests: This code is issued by the server if it receives too many requests from a client within a certain period of time. This can happen, for example, if an SEO tool queries too many keywords in the Google search engine in a short period of time.
- 431 request header fields too large: If the length of the header field or the entire header has been exceeded, this status code appears.
Avoid errors
Errors with status code 400 are usually caused by the web browser settings. Therefore, users must check which websites are emitting these errors. At the same time, the server may return an error code of 400 if the user entered a character in a field on the form that was not intended. Therefore, if you receive a user error with status code 400, you must modify your software or your inputs.
Troubleshooting 404
The classic 404 error is equally annoying for webmasters and users. If 404 errors pile up, this is a sign of a poorly maintained website for users and search engines. It would be wise to create a special 404 error page so as not to negatively affect usability.
Humor is usually used on 404 error pages. This will encourage users and make them continue on the page and search for the desired content on the landing page.
Another opportunity is to provide a search bar to the right of the 404 page, so that the desired information can be found. Alternatively, it is feasible to list similar topics.
Here are 7 specific tips on what a 404-error page should contain:
- Polite or humorous apology for the mistake.
- Alternatives to the desired page, the desired product (for example, online stores) or alternative posts (such as blogs).
- Option for the user to report the error so that it can be removed.
- Direct reference to the main navigation.
- A separate search bar to search for more content.
- Design of the error page in accordance with the corporate design so that it is not perceived as a foreign object.
- Contact options.
If you manage to keep the visitor on your website despite a 404 error page, the purpose of such a page would be achieved and the bounce rate would be reduced and certainly still convert.
Web Links
