Buzz
HTTP status codes convey important information to users. If you own a website, understanding the 404 Not Found error and some common HTTP errors can help improve your website's ranking on Google's search engine.
Understanding status codes
Behind every error message you see on a website lies an HTTP status code sent by the server. The status code is a three-digit number. The first digit signifies the class of the status code:
- Status code 1XX provides information.
- 2XX indicates success.
- 3XX is for redirection.
However, errors you typically encounter belong to status codes 4XX and 5XX:
- 4XX denotes client-side errors.
- 5XX indicates issues from the server side.
HTML errors on the page are displayed in these cases because the client doesn't know how to proceed.
404 Not Found Error and Some Common HTTP Errors
Errors from the client side (4XX error codes)
1. 400 - Bad Request Error
Whenever the client sends a request to the server that the server doesn't understand, the website displays a 400 Bad Request error. This error typically occurs when the data sent by the browser doesn't adhere to the rules of the HTTP protocol, so the server doesn't know how to handle a request containing incorrectly formatted syntax.
If you encounter a 400 error message, it's likely due to client-side issues, such as: inadequate operating system protection, unstable internet connection, browser errors, or cache memory issues.
The ideal solution is to first check your internet connection, browser, and computer before contacting the website owner.
First, try reopening the same website on a different browser, clearing the cache memory, and checking if any security updates need to be installed. If you frequently encounter 400 errors when opening other websites, it may be because your computer or Mac is awaiting security update installations.
2. 401 - Authorization Required Error
When a website protected by a password upon client request, the server responds with a 401 Authorization Required error code. The 401 error doesn't immediately return a traditional error message; instead, a popup window appears on the screen asking the user to provide login credentials.
If you provide the login credentials, everything will be fine, and you can continue accessing the protected website without any issues. Otherwise, you'll be redirected to a page displaying the Authorization Required error message.
If you're a website owner, you can add the same password protection to your website or a portion of your website through cPanel.
Click on Password Protect Directories in the Security menu and select the web directory you want to protect. It's a good security measure to restrict access to your admin area, such as the wp-admin directory on a WordPress website.
3. 403 - Forbidden Error
When the server understands the client's request but refuses to execute it for some reason, you'll see a 403 Forbidden error message on the screen. This error isn't an authorization issue. Returning a 403 status code means the server is denying the client without any explanation.
Common reasons for this error include website owners not wanting visitors to browse through the file directory structure of the website. When this protection type is activated, you can't directly access directories on the website. Another reason is specific files that the client requests aren't allowed to be viewed on the web.
For security reasons on your website, you can set up 403 protection. This ideal solution protects your website from attacks by hiding directory or file structures containing vulnerable information.
The good news is that many web servers provide this translation by default for their clients. But if you want to add an extra layer of security, open your cPanel account and navigate to Menu Advanced, then select Index Manager.
Here, you can customize how visitors view a specific directory on your website. If you choose No Indexing, when a client attempts to access a specific directory, they will receive a 403 error message.
4. 404 - Not Found Error
404 is currently the most common HTTP status code. The web browser returns a 404 HTML page when the server cannot find anything at the requested location.
There are two main reasons for the 404 Not Found page error. Firstly, it could be due to the visitor entering the wrong URL, or secondly, it could be because the website's permalink structure has been altered, and incoming links have been redirected to different locations.
Typically, the 404 error occurs due to visitors inputting the wrong URL. The error occurs when a website is moved to a new web server and the DNS still points to the old location of the page. This type of error usually disappears after some time.
Many SEO experts believe that the 404 Not Found error and some common HTTP errors may negatively impact your website's search engine ranking. However, Google states that the 404 error does not affect your website's ranking in Google search, and you can ignore the error because search engines consider 404 errors as a normal part of a website.
The most common solution to reduce 404 errors is to use 301 redirects for permanently deleted pages and 302 redirects for temporarily unavailable pages.
5. 408 - Request Time-Out Error
When the client's request takes too long, the server times out, closes the connection, and the browser displays a 408 Request Time-Out error message.
Time-Out errors occur because the server does not receive a complete request from the client within the time it's prepared to wait. The 408 error can occur due to the workload the server is handling or the client system being overloaded.
In some cases, both ends of the connection operate normally, but a temporary slow internet connection delays message transmission. Large websites often address 408 errors similar to how you would fix a 404 error. Additionally, the 408 error can be resolved by pressing the F5 key to refresh the page.
6. 410 - Gone Error
The 410 error is quite similar to the 404 error. Both errors occur because the server cannot find the requested file, but while the 404 error indicates that the target file may be available somewhere on the server, the 410 error signifies permanence.
The 410 error informs the client that the intentionally unavailable resource has been removed, and the website owner wants to remove incoming links from the Web. The 404 error is used when the server is uncertain if permanently unavailable files exist, but the 410 error always indicates complete certainty.
If you manage your own server, it's important to understand how Google's crawlers handle 404 and 410 errors. Matt Cutts, head of Google's search and spam team, has explained this difference. The ideal solution is to understand the difference between 404 and 410 errors to enhance Google friendliness.
Errors from the server side (5XX error codes)
7. 500 - Internal Server Error
The Internal Server Error is the most common server error. It occurs whenever the server encounters unexpected conditions, preventing it from fulfilling the client's request. The 500 error code is a generic error code returned when no other 5XX error code is returned from the server.
Although this issue cannot be resolved at its root, you can apply some temporary solutions to troubleshoot the problem, such as refreshing the page (as the error may be temporary), clearing browser cache (as the cause of the problem may be the version stored in the website's cache memory), clearing browser cookies, and restarting the browser.
Additionally, you can contact the Webmaster (website administrator) (similarly to other server issues) so they can address any issues on their website.
If encountering a 500 error on your own website, you should reach out to your hosting provider. The cause may be permissions, a faulty .htaccess file, or low memory limits. If your website is WordPress, a third-party plugin could be causing the 500 error. Try troubleshooting by disabling each plugin until you identify the culprit as the cause.
8. 502 - Bad Gateway Error
The 502 error occurs when there is a communication issue between two servers. It happens when the client connects to a server acting as a gateway or proxy that needs to access a server providing additional services for it.
Another server is positioned higher in the server hierarchy. It could be an Apache web server accessed by a proxy server, or a server of a large Internet service provider accessed by a local server.
When encountering a Bad Gateway error, the server receives an invalid response from the source server.
In most cases, the error does not imply that the source server is down, but rather that the two servers are not in agreement on how to exchange data over the protocol.
This often occurs when one of the servers is misconfigured or improperly programmed. Contact your hosting service provider if you encounter a 502 error on your own website.
9. Error 503 - Service Temporarily Unavailable
The Service Temporarily Unavailable error (or sometimes Out of Resources error) occurs when the server is temporarily overloaded, or when the server is undergoing routine maintenance. The 503 error code means the web server is currently unavailable. These temporary conditions will be resolved after a delay.
As a website owner, it's important to have knowledge about the 503 status code to handle maintenance properly. Failure to handle routine maintenance correctly may negatively impact your website's search engine ranking.
10. Error 504 - Gateway Time-Out
Gateway Time-Out error occurs equivalently to a communication issue between servers, similar to the 502 Bad Gateway error. When the 504 status code is returned, a higher-tier server is responsible for sending data to the server connected to the client. In this case, the lower-tier server does not receive a timely response from the source it accesses.
This time-out issue is similar to the 408 Request Time-Out status code but does not occur between the client and server but between two servers in the backend. The Gateway Time-Out error indicates a slow communication process between two servers, and the error may also occur when the higher-tier server is completely down.
Error 504 is also related to network connection issues, only those with access rights to that network can fix the error. Like other server-side HTTP errors, sometimes simply refreshing the page, reloading the page can resolve the issue, of course, only network service providers can do this.
Here Mytour has just provided you with a list of 404 Not Found errors and some common HTTP errors, as well as how to troubleshoot common web browsing errors. If you have any questions, please leave your question in the comments section below the article!
