Error codes
100-199 : Informational status
200-299 : Success status
300-399 : Redirection status
400-499 : Client errors
500-599 : Server errors
400 – Bad Request – You probably typed in a URL wrong, the server has no clue what you’re looking for, or you aren’t allowed to have access. Usually, it’s a matter of the URL being typing in wrong. Maybe you mixed upper and lowercase letters or something.
401 – Unauthorized Request – you tried to get to something on the web server you’re not allowed to play with. In other words, you ain’t on the party list.
403 – Forbidden – You can’t access the page. You may not have access (it may require a password), or it may be blocked from your domain.
404 – Not Found – The page you were trying to look at was not found on the server. This is probably the most common error you’ll come across. What has probably happened is that the web page you were going to has been removed or re-named.
500 – Internal error – Usually caused by a CGI error. You fill out a form, but the script used to process it is not working properly.
503 – Service Unavailable – The server may be overloaded, down, or have other similar problems. Try later.
100 Continue
101 Switching Protocols
The 200 status code is by far the most common returned. It means, simply, that the request was received and understood and is being processed.
201 Created The request was successful and a new resource was created (for example a new page).
The status code 202 indicates that server has received and understood the request, and that it has been accepted for processing, although it may not be processed immediately.
A 203 status code means that the request was received and understood, and that information sent back about the response is from a third party, rather than the original server. This is virtually identical in meaning to a 200 status code.
204 No Content The server has processed the request but there is no new information to be returned
205 Reset Content The 205 status code is a request from the server to the client to reset the document from which the original request was sent. For example, if a user fills out a form, and submits it, a status code of 205 means the server is asking the browser to clear the form.
A status code of 206 is a response to a request for part of a document. This is used by advanced caching tools, when a user agent requests only a small part of a page, and just that section is returned.
The 300 status code indicates that a resource has moved. The response will also include a list of locations from which the user agent can select the most appropriate.
A status code of 301 tells a client that the resource they asked for has permanently moved to a new location. The response should also include this location. It tells the client to use the new URL the next time it wants to fetch the same resource.
A status code of 302 tells a client that the resource they asked for has temporarily moved to a new location. The response should also include this location. It tells the client that it should carry on using the same URL to access this resource.
A 303 status code indicates that the response to the request can be found at the specified URL, and should be retrieved from there. It does not mean that something has moved - it is simply specifying the address at which the response to the request can be found.
The 304 status code is sent in response to a request (for a document) that asked for the document only if it was newer than the one the client already had. Normally, when a document is cached, the date it was cached is stored. The next time the document is viewed, the client asks the server if the document has changed. If not, the client just reloads the document from the cache.
A 305 status code tells the client that the requested resource has to be reached through a proxy, which will be specified in the response.
A status code of 400 indicates that the server did not understand the request due to bad syntax.
A 401 status code indicates that before a resource can be accessed, the client must be authorised by the server.
The 402 status code is not currently in use, being listed as "reserved for future use".
A 403 status code indicates that the client cannot access the requested resource. That might mean that the wrong username and password were sent in the request, or that the permissions on the server do not allow what was being asked.
The best known of them all, the 404 status code indicates that the requested resource was not found at the URL given, and the server has no idea how long for.
A 405 status code is returned when the client has tried to use a request method that the server does not allow. Request methods that are allowed should be sent with the response (common request methods are POST and GET).
The 406 status code means that, although the server understood and processed the request, the response is of a form the client cannot understand. A client sends, as part of a request, headers indicating what types of data it can use, and a 406 error is returned when the response is of a type not in that list.
The 407 status code is very similar to the 401 status code, and means that the client must be authorized by the proxy before the request can proceed.
A 408 status code means that the client did not produce a request quickly enough. A server is set to only wait a certain amount of time for responses from clients, and a 408 status code indicates that time has passed.
A 409 status code indicates that the server was unable to complete the request, often because a file would need to be edited, created or deleted, and that file cannot be edited, created or deleted.
A 410 status code is the 404's lesser known cousin. It indicates that a resource has permanently gone (a 404 status code gives no indication if a resource has gine permanently or temporarily), and no new address is known for it.
The 411 status code occurs when a server refuses to process a request because a content length was not specified.
A 412 status code indicates that one of the conditions the request was made under has failed.
The 413 status code indicates that the request was larger than the server is able to handle, either due to physical constraints or to settings. Usually, this occurs when a file is sent using the POST method from a form, and the file is larger than the maximum size allowed in the server settings.
The 414 status code indicates the the URL requested by the client was longer than it can process.
A 415 status code is returned by a server to indicate that part of the request was in an unsupported format.
A 500 status code (all too often seen by Perl programmers) indicates that the server encountered something it didn't expect and was unable to complete the request.
The 501 status code indicates that the server does not support all that is needed for the request to be completed.
A 502 status code indicates that a server while acting as a proxy, received a response from a server further upstream that it judged invalid.
A 503 status code is most often seen on extremely busy servers, and it indicates that the server was unable to complete the request due to a server overload.
504 Gateway Time-Out
A 505 status code is returned when the HTTP version indicated in the request is no supported. The response should indicate which HTTP versions are supported.
No comments:
Post a Comment