Common Web Application Error Codes
Contents |
2009 in Tech blog Sometimes when you try to visit web page, you’re met with an HTTP error message. It’s a message from the web server that something went wrong. In some cases it could be a mistake you made, but often it’s the site’s fault. Each type windows application error codes of error has an HTTP error code dedicated to it. For example, if you try to common http error codes access a non-existing page on a website, you will be met by the familiar 404 error. Now, you might wonder, which are the most common HTTP common sql error codes errors that people encounter when they surf the Web? That is the question we’ll answer in this article. Google to the rescue Why not let millions of Web users tell us themselves what errors they encounter the most? In an indirect web server error codes way we can do that via Google. The basic idea here is that some of the people who encounter errors when they visit websites will want to know more about that error, and will go to the nearest search engine to do so. In short, Google’s search statistics should in this case be able to give us a pretty good idea of which HTTP errors are most common. Using Google Insights for Search (a great tool for estimating the “popularity” of search terms) we
Common Web Application Vulnerabilities
went through all of the different HTTP error codes that exist, comparing them against each other. When the dust settled from this little shootout, we had the top list you can see here below. The top 5 errors, according to Google Here they are, listed and explained in reverse order, the five most common HTTP errors. Drumroll, please… 5. HTTP error 401 (unauthorized) This error happens when a website visitor tries to access a restricted web page but isn’t authorized to do so, usually because of a failed login attempt. 4. HTTP error 400 (bad request) This is basically an error message from the web server telling you that the application you are using (e.g. your web browser) accessed it incorrectly or that the request was somehow corrupted on the way. 3. HTTP error 403 (forbidden) This error is similar to the 401 error, but note the difference between unauthorized and forbidden. In this case no login opportunity was available. This can for example happen if you try to access a (forbidden) directory on a website. 2. HTTP error 404 (not found) Most people are bound to recognize this one. A 404 error happens when you try to access a resource on a web server (usually a web page) that doesn’t exist. Some reasons for this happening can for example be a broken link, a mistyped URL, or that the webmaster has moved the requested page somewhere else (or deleted it). To counter the ill effect of broken links, so
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
Common Web Application Vulnerabilities And Attacks
the browser’s address bar, requests and responses have a predefined structure. As defined by common web application architectures the Hypertext Transfer Protocol (HTTP), an important part of that structure is a status code. Introducing HTTP Status Codes Status codes are common beep codes three-digit numbers. A 200 code is the most common and represents a successful response. The first digit defines what is known as the class of the status code. If the code starts with a 2, as in http://royal.pingdom.com/2009/05/06/the-5-most-common-http-errors-according-to-google/ 200, that represents a successful response to the request. There are status codes that start with 1. These represent informational messages. These are rarely seen. A code of the form 3xx represents a redirection response. Typically, the browser will handle these without user interaction and get the resource from the new location instead. Error codes come in the form of 4xx and 5xx statuses. Error codes at the 400 level mean there was a https://www.globo.tech/learning-center/5-most-common-http-error-codes-explained/ 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. Let’s look at each of these in a little more detail. 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 40
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e This is a list of Hypertext Transfer Protocol https://en.wikipedia.org/wiki/List_of_HTTP_status_codes (HTTP) response status codes. It includes codes from IETF internet standards, other IETF RFCs, http://www.practicalecommerce.com/articles/80-Understanding-Common-Web-Error-Messages other specifications, and some additional commonly used codes. The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part error codes of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information,[3] but not all of those are here (note that these sub-codes only appear in the response payload and in documentation; not in the place of an actual HTTP status code). Contents 1 1xx Informational 2 2xx common web application Success 3 3xx Redirection 4 4xx Client Error 5 5xx Server Error 6 Unofficial codes 6.1 Internet Information Services 6.2 nginx 6.3 CloudFlare 7 See also 8 Notes 9 References 10 External links 1xx Informational[edit] Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. The response 417 Expectation Failed indicates the request should not be continued.[2] 101 Switching Protocols The requester has asked the server to switch protocols
Articles » Design & Development » Understanding Common Web Error Messages October 1, 2005 • Practical Ecommerce Print Tweet 0 Over the years in the interactive marketing business, any consultant worth his or her salt has faced the dilemma of assisting a company whose primary issue is that its “Web site broke.” No more information than that. “It broke.” Many a parent can identify with this description as it pertains to children who say that they “hurt,” but can’t identify from exactly where the pain originates. Fortunately for Web consultants — and for ecommerce proprietors — there are and always have been very simple, easy-to-understand error message standards for the Internet. Those messages are your keys to resolving Web problems, for yourself and for your customers. We’ll examine the most common Web site errors, and provide easy ways to resolve them. Let’s say you open a browser, and start surfing your site. Oh dear, you’ve encountered an error message … If it’s: 400 Bad File Request: There is something syntactically wrong with the request from the browser to the server. Retype the URL, paying close attention to letter case and special characters. 401 Unauthorized: The request from the browser to the server requires authentication. More than likely this indicates that a username and password was required to access the page, and you didn’t enter the correct pair. 403 Forbidden: The request from the browser to the server was understood, but the server has been instructed not to respond with a Web page. More than likely, there is a server permission issue – and that can be a conundrum for the ecommerce business owner, particularly if he or she is also a novice Web server administrator. The resolution to this problem is to go to the server, select the file in question and give global users read and execute permissions. For those of you with UNIX knowledge, you’ll want to chmod your fi