| |
200 Document follows | The request has been fulfilled and an entity corresponding to the requested resource is being sent in the response. |
201 Created | The request has been fulfilled and resulted in a new resource being created. |
202 Accepted | The request has been accepted for processing, but the processing has not been completed. |
203 Provisional information | The returned meta information in the Entity-Header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. |
204 No Content | The server has fulfilled the request but there is no new information to send back. If the client is a user agent, it should not change its document view. |
300 Moved | The requested resource is available at one or more locations and a preferred location could not be determined via content negotiation. |
301 Moved permanently | Requires the \QLocation' header, see the <head> tag. The requested resource has been assigned a new permanent URI and any future references to this resource must be done using the returned URI. |
302 Moved temporarily | Requires the \QLocation' header, see the <head> tag. The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, the client should on future requests from the user continue to use the original Request-URI and not the URI returned in the URI-header field and Location fields. |
304 Not modified | The document has not been modified. |
400 Bad Request | The request had bad syntax or was inherently impossible to satisfy. The client is discouraged from repeating the request without modifications. |
401 Access denied | The request requires user authentication. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The client may repeat the request with a suitable Authorization header field. This might, for instance, be used inside a <deny user=...> tag. |
402 Payment Required | The user has to pay you to get the information. |
403 Forbidden | The request is forbidden for a reason that is unknown to the client. |
404 No such file or directory | The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. |
405 Method not allowed | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. |
408 Request timeout | n/a |
409 Conflict | n/a |
410 This document is no more | The requested resource is no longer available at the server and no forwarding address is known. |
500 Internal Server Error | n/a |
501 Not implemented | n/a |
502 Service Unavailable | n/a |
503 Gateway Timeout | n/a |