You’ve got an Error! There is a fix.
A glossary of everyday HTTP errors and how to fix them
Let’s face it, you must have come across some web error, at least once in your lifetime on the internet. We all have. It irritates the life out of me. You are trying to look up a website or at the middle of an intense search spree for a project and BAM, the internet delivers its message!
So, what these errors actually are, what’s causing them, and how we fix them!?
What is a Web Error?
A web error, also known as an HTTP (Hyper Text Transfer Protocol) error, is an error message displayed when a problem occurs during the communication between a web browser and a web server. When a web browser sends a request to a web server to access a specific page or resource, the server can respond with an HTTP status code to indicate the outcome of the request. Some status codes, such as 200 (OK), indicate a successful request, while others, such as 404 (Not Found), indicate an error has occurred.
HTTP errors can be caused by a variety of issues, including incorrect URLs, server malfunctions, network problems, or client-side problems, such as incorrect form submissions or browser compatibility issues.
Let's dive a bit deeper and find out why these errors occur, what these weird-looking numbers on our screen actually mean, and how we can fix them!
Client-side errors:
These errors occur on web browsers, due to issues such as incorrect URL syntax, unsupported browser versions, or outdated software. Some common examples of these errors are:
404 Error (Not Found):
This error occurs when we try to access a URL that doesn’t exist on the server. For example, you may try to access “www.example.com/invalidpage" and receive a 404 error because the page doesn’t exist.
400 Error (Bad Request):
This error occurs when we send an invalid request to the server. For example, you may submit a form with incorrect information, such as an invalid email address, and receive a 400 error.
How to fix it?
- Check the URL for typos and correct them if necessary.
- Try refreshing the page or clearing your browser cache and cookies.
- If the page has been moved or deleted, search the website or contact the website owner for more information.
Server-side errors:
These errors occur on the server side and are usually caused by issues such as incorrect configurations, overloaded servers, or server maintenance.
500 Error (Internal Server Error):
This error occurs when the server encounters an unexpected condition that prevents it from fulfilling the request. For example, a server-side script may encounter a syntax error and generate a 500 error.
503 Error (Service Unavailable):
This error occurs when the server is temporarily unable to handle the request due to maintenance, overloading, or other reasons. For example, a website may generate a 503 error during a server upgrade.
How to fix it?
- Try refreshing the page or clearing your browser cache and cookies.
- Check the server logs or contact the website owner for more information.
- If you are the website owner, try restarting the web server or checking the server configuration for errors.
Network errors:
These types of errors occur due to issues with the network infrastructure, such as slow or unreliable connections, firewall restrictions, or routing problems.
408 Error (Request Timeout):
This error occurs when the client takes too long to send a request, and the server closes the connection. For example, you may experience a 408 error due to a slow internet connection.
502 Error (Bad Gateway):
This error occurs when the server acting as a gateway or proxy is unable to receive a valid response from the upstream server. For example, you may receive a 502 error if a server is temporarily down or if there is a problem with the network infrastructure.
How to Fix?
- Try refreshing the page or clearing your browser cache and cookies.
- Check your internet connection and try again.
- If the error persists, contact your internet service provider for more information.
Application errors:
These errors occur due to issues with the underlying application, such as bugs, coding errors, or compatibility problems.
406 Error (Not Acceptable):
This error occurs when the server cannot produce a response that matches the accept headers sent by the client. For example, you may receive a 406 error if you request a specific format, such as JSON, that is not supported by the server.
417 Error (Expectation Failed):
This error occurs when the server is unable to fulfill the expectations set in the request headers. For example, you may receive a 417 error if the request includes an “Expect: 100-continue” header and the server does not support this feature.
How to Fix?
- Check the request headers and make sure the correct content type is specified.
- If the error persists, contact the website owner for more information.
Resource errors:
These errors occur we request a resource that is not available, such as a missing file, invalid URL, or unsupported format.
410 Error (Gone):
This error occurs when you requests a resource that has been permanently removed from the server. For example, you may receive a 410 error if you try to access a page that has been deleted.
429 Error (Too Many Requests):
This error occurs when we make too many requests in a short period of time and the server rate-limits the client. For example, you may receive a 429 error if you make too many API requests in a short amount of time.
How to Fix?
- If the resource has been permanently removed, search the website for similar resources or contact the website owner for more information.
- Wait a few minutes and try accessing the resource again.
- If the error persists, contact the website owner for more information.
Protocol errors:
These errors occur when there is a mismatch between the client and server in terms of supported protocols or version numbers.
505 Error (HTTP Version Not Supported):
This error occurs when the server is unable to support the version of the HTTP protocol used in the request. For example, you may receive a 505 error if you use an outdated web browser that supports an older version of HTTP.
511 Error (Network Authentication Required):
This error occurs when the client needs to authenticate to access a network resource. For example, you may receive a 511 error if you try to access a secure website without logging in.
How to Fix?
- Check the version of your web browser and update it if necessary.
- If the error persists, contact the website owner for more information.
- Log in to the network or website if necessary.
- If the error persists, contact the website owner or your internet service provider for more information.
In Conclusion, These are just a few examples of each type of HTTP error, that we encounter on an everyday basis. These are just general tips and the solution may vary depending on the specific circumstances of each error. But at least you now know a bit about them and won’t freak out instantly like I always did, and hopefully will be able to do the First Aid by yourself. However, If you are unable to resolve the error, it is always a good idea to contact the website owner or your internet service provider for more information and assistance.
Found it Useful?
Then don’t for to spread the word with just a little CLAP!
Happy Reading!
Follow me for more interesting articles!
