When you surf the web, it works on a request-response system. You request a resource, such as web page or an image, and you get back a response, or your browser does, at least. Thanks to the “http:” you place before a URL when you type in the browser’s address bar, requests and responses have a predefined structure. As defined by the Hypertext Transfer Protocol (HTTP), an important part of that structure is a status code.
Introducing HTTP Status Codes
Status codes are three-digit numbers.
· Code starts with a 1. These represent informational messages. These are rarely seen.
· Code starts with a 2, as in 200, that represents a successful response to the request.
· Code starts with a 3 in form 3xx represents a redirection response.
· Error codes at the 400 level mean there was a client-side error — think of something like the user typing the wrong URL in the address bar.
· Error codes at the 500 level mean there was a server-side error — think of something like the database server going down or perhaps running out of disk space.
Five of the most popular error codes are 403, 404, 500, 503, and 504.
404 Not Found
The most common error code you run into is a 404 error. The 404 status code means the requested resource is no longer available or, more specifically, just not found. Was it ever available there? You don’t know. You do know it isn’t available there now.
What are some of the reasons for a 404 error? Typos are a common reason for getting a 404 error. A missing or extra letter in a typed-in url, or a wrong domain name can often result in a 404 error. Another reason for 404 errors isn’t typos; it is the aging of the web. When someone writes an article or blog, that person might link to a secondary source to provide additional information for the article. Now imagine revisiting said article six months or six years later. If what was linked to is no longer on the web, a 404 error will be generated when you click on the link in the browser.
403 Forbidden
Another common client-side response status code is 403. Getting a 403 status code back from an HTTP request means access to the resource is forbidden. This is not an authentication problem; those are 401 (unauthorized) errors. One common reason for 403 errors is the server maintaining a whitelist of machines that can access that system and the user’s machine not being on it. If the client’s certificate is no longer valid (or is just plain missing), that’s another reason for a 403 error response. There typically is no recovery from these, short of trying from a different machine. Finally, there’s also the possibility of wrong permissions associated to files. Often in Linux and sometimes in Windows, a webserver will not have access to website files because of faulty permissions. This will also result in a 403 error. The server owner will need to change the file permissions to fix this.
500 Internal Server Error
Moving over to the server-side error codes, the 500 error is the catchall. When none of the other 500 error codes make sense, or if the programmer is just lazy and doesn’t identify the specific problem, a 500 status code is returned. Typically, you can retry the request attempt again and possibly get a different response. Of course, retrying attempts that involved a shopping cart that resulted in a 500 error could result in a duplicate order, so tread carefully there.
503 Service Unavailable
Like many of the 500-level error codes, the 503 (service unavailable) status code could be a temporary problem. It basically means the web server isn’t available. Why? You don’t know. Perhaps the web server just restarted and is in the middle of initialization. Perhaps it is overloaded and can’t handle any more concurrent requests. Or perhaps it is just down for maintenance. Retrying the request could work or could return another 5xx error.
504 Gateway Timeout
The final of the top five error codes is the 504 status, indicating a gateway timeout. The name says it all. A proxy server needs to communicate with a secondary web server, such as an apache server, and access to that server timed out. There could be a DNS issue, a network device might be down, or the other machine could just be overly busy and unable to process the request in a timely fashion. This can only happen in a setup where a caching or proxy server is directly serving the webpage and the actual webserver behind it is unreachable. As with the other 5xx-level errors, just retrying the request could result in a successful response.
In the End
HTTP and its associated secure HTTPS are the primary protocols for browsing on the web. Each web request results in a response with an associated status code. Status codes fall into classes: informational (1xx), success (2xx), redirection (3xx), client errors (4xx), server errors (5xx). You try to get success responses with your requests, but it doesn’t always happen. Learn how to recover from these error codes, so you can move on.
Hope this helps.
Regards,
Arun
No comments:
Post a Comment