{"id":16969,"date":"2020-11-12T04:13:19","date_gmt":"2020-11-11T20:13:19","guid":{"rendered":"https:\/\/web.mwwsb.com.my\/pjci\/?post_type=kb&p=16969"},"modified":"2022-09-08T21:41:40","modified_gmt":"2022-09-08T13:41:40","slug":"common-http-errors-and-how-to-troubleshoot-them","status":"publish","type":"kb","link":"https:\/\/www.casbay.com\/guide\/kb\/common-http-errors-and-how-to-troubleshoot-them","title":{"rendered":"Common HTTP errors and how to troubleshoot them"},"content":{"rendered":"\t\t
By reading this article, you can learn about different series codes. Also, we will guide you on the ways to troubleshoot some common HTTP errors. These errors include:<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
Well, now let’s start with errors from<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
We consider the status codes in the 400 range to be client error codes. These kinds of error codes are often security-related. Moreover, we can also return the 400 level error codes if the request is malformed OR if the client times out.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
The 400 status code, or Bad Request error, means the HTTP request that we sent to the server has invalid syntax.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
Here are a few examples of when a 400 Bad Request error might occur:<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
The 401 status code, or an Unauthorized error, means that the user trying to access the resource has not been authenticated or has not been authenticated correctly. This means that the user must provide credentials to be able to view the protected resource.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
To fix a 401 error, try turning off password protection in cPanel or use the correct username and password.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
The 403 status code, or a Forbidden error, means that the user made a valid request but the server is refusing to serve the request, due to a lack of permission to access the requested resource. Furthermore, 403 errors commonly occur when the user that is running the web server process does not have sufficient permissions to read the file.<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t By default, servers display this error instead of a website\u2019s file structure if the browser cannot find the website\u2019s home page.<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Index Page Missing:<\/span><\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Index Page Misspelled:<\/span><\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Redirect with no Index Page:<\/span><\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Lack of permission to access the requested resource:<\/span><\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t The 404 status code, or a Not Found error, means that the user is able to communicate with the server but it is unable to locate the requested file or resource.<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t 404 errors can occur in a large variety of situations. If the user receives an error of 404 Not Found unexpectedly. Here are a few issues to ask during troubleshooting:<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Web browsers make a request for information from the server. When this happens, it sends an Accept header. This tells the server in what formats the browser can accept the data. If the server cannot send data in a format requested in the Accept header, the server sends the 406 Not Acceptable error. The cause of the 406 error is usually due to a mod_security rule on the server. Mod_security is a security module in the Apache web server that is enabled by default on all hosting accounts.<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t4) 404 Not Found<\/b><\/h5>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
5) 406 Not Acceptable<\/b><\/h5>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t