Lorem Ipsum
Free dummy text generator
Lorem Ipsum

Htaccess redirects

Search Engine Optimization Tools


ASCII Characters

Client Information
What is HTTP status codes?
HTTP status codes are traffic/responses from servers on the Internet. There are different answers/responses - too many to remember all.

To make it easy to find out what a specific response means, lorem.biz has prepared an easy to read table below where you find all http status codes.

HTTP status codes
1xx Informational
Request received, continuing process.
Code Status Explanation
100 Continue This means that the server has received the request headers, and that 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).
101 Switching Protocols When requesting a page, a browser might receive a status code of 101, followed by an "Upgrade" header showing that the server is changing to a different version of HTTP.
102 Processing (WebDAV) This is a HTTP status code shown when WebDAV is processing.
122 Request-URI too long A Microsoft extension which occurs only in IE7, when the request URI is longer than 2032 characters, the maximum string length.
2xx Success
The action was successfully received, understood, and accepted.
Code Status Explanation
200 OK Standard response for HTTP successful requests.
201 Created The request has been fulfilled and resulted in a new resource being created. When new pages are created by posted form data or by a CGI process, this is confirmation that it worked.
202 Accepted The client's request was accepted, though not yet processed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
203 Non-Authorative Information The information contained in the entity header is not from the original site, but from a third party server.
204 No Content If you click a link which has no target URL, this response is elicited by the server. It is silent and does not warn the user about anything.
205 Reset Content This allows the server to reset any content returned by a CGI.
206 Partial Content The requested file was not downloaded entirely. This is returned when the user presses the stop button before a page is loaded, for example, or split a download into multiple simultaneous streams.
3xx Redirection
The client must take additional action to complete the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD.
Code Status Explanation
300 Multiple Choices Indicates multiple options for the resource that the client may follow. Example: The requested address refers to more than one file. Depending on how the server is configured, you get an error or a choice of which page you want.
301 Moved Permanently If the server is set up properly it will automatically redirect the reader to the new location of the file. You should use this redirect when working with SEO.
302 Moved Temporarily Page has been moved temporarily, and the new URL is available. You should be sent there by the server.
303 See Other The response to the request can be found under another URI using a GET method. Data is somewhere else and the GET method is used to retrieve it. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
304 Not Modified If the request header includes an 'if modified since' parameter, this code will be returned if the file has not changed since that date. Search engine robots may generate a lot of these. Utilizing this saves bandwidth and reprocessing on both the server and client.
305 Use Proxy The recipient is expected to repeat the request via the proxy. Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
306 Switch Proxy Not used.
307 Temporary Redirect In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to http status code 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
4xx Client Error
The client failed to provide an valid request.
Code Status Explanation
400 Bad Request There is a syntax error in the request, and it is denied.
401 Authorization Required The request header did not contain the necessary authentication codes, and the client is denied access.
402 Payment Required Payment is required. This code is not in operation.
403 Forbidden The request was a legal request, but the server is refusing to respond to it. This is also returned at times when the server does not want any more visitors.
404 Not Found The requested file was not found on the server. Possibly because it was deleted, or never existed before. Often caused by misspellings of URLs.
405 Method Not Allowed The method you are using to access the file is not allowed. Examples: using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
406 Not Acceptable The requested file exists but cannot be used as the client system does not understand the format the file is configured for.
407 Proxy Authentication Required The request must be authorised before it can take place.
408 Request Timed Out The server took longer than its allowed time to process the request. Often caused by heavy internet traffic.
409 Conflicting Request Too many concurrent requests for a single file.
410 Gone The file used to be in this position, but is there no longer. This should be used when a resource has been intentionally removed; however, in practice, a 404 Not Found is often issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes to prevent repeated requests.
411 Content Length Required The request is missing its Content-Length header.
412 Precondition Failed A certain configuration is required for this file to be delivered, but the client has not set this up.
413 Request Entity Too Long The requested file was too big to process.
414 Request URI Too Long The address you entered was too long for the server.
415 Unsupported Media Type The filetype of the request is unsupported.
416 Requested Range Not Satisfiable The client has asked for a portion of the file, but the server cannot supply that portion (for example, if the client asked for a part of the file that lies beyond the end of the file).
417 Expectation Failed You get Expectation Failed as response.
422 Unprocessable Entity Used with WebDAV. The request was well-formed but was unable to be followed due to semantic errors.
423 Locked Used with WebDAV. The resource that is being accessed is locked.
424 Failed Dependency Used with WebDAV. The request failed due to failure of a previous request (e.g. a PROPPATCH).
425 Unordered Collection Used with WebDAV. Defined in drafts of WebDav Advanced Collections, but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol"
426 Upgrade Required The client should switch to TLS/1.0.
449 Retry With A Microsoft extension. The request should be retried after doing the appropriate action.
450 Blocked A Microsoft extension. Used for blocking sites with Windows Parental Controls.
5xx Server Error
The server failed to fulfill an apparently valid request.
Code Status Explanation
500 Internal Server Error A response that is usually caused by a problem in your code.
501 Not Implemented The request cannot be carried out by the server.
502 Bad Gateway The server you are trying to reach is sending back errors.
503 Service Unavailable The service or file that is being requested is not currently available.
504 Gateway Timeout The gateway has timed out. Like the http status code 408 timeout error, but this one occurs at the gateway of the server.
505 HTTP Version Not Supported The HTTP protocol you are asking for is not supported.
506 Variant Also Negotiates HTTP staus code Variant Also Negotiates.
507 Insufficient Storage Used with WebDAV. You get this HTTP staus code when you have Insufficient Storage.
509 Bandwidth Limit Exceeded HTTP staus code Bandwidth Limit Exceeded.
510 Not Extended HTTP staus code Not Extended.

Start | Lorem Ipsum dummy text | Lorem Ipsum source

Simple Page | Simple Folder | New Start Page | New File Extension | Non-www to www-domain | www to non-www-domain | Old Domain to New Domain

Keyword Suggestion Tools | Keyword Density Tools | Keyword Tracking Tools | Backlink Tools | Duplicate Content Check | Search Engine Saturation Tools | Search Engine Simulator Tools | Google PageRank Check | Yahoo WebRank Check | Meta Tag Generator | Robots Generator | Domain Statistics Tools | Website to Country

Word and Letter Count Tool | HTTP Status Codes

ASCII table | Extended ASCII | HTML Codes

My IP Address | My screen resolution | My color depth | My operative system | My web browser


Web lorem.biz