TmP - HTTP




[ index \| glossary \| news \| downloads \| links ]


	HTTP working HTTP/0.9 HTTP/1.0 HTTP/1.1 HTTP/1.0 status HTTP/1.1 status HTTP/1.1 directives news glossary links downloads credits contact



	search

last update 19/02/2003

HTTP/1.1 status

These status complete those from HTTP/1.0. The novelty is the definition of 2 status for the 1xx class. The 4xx class has been dramatically completed.

1xx - Informational

These status provide a temporary response. There is no special header for these status.

A 1xx status must not be sent to a HTTP/1.0 client, except for experimental circumstances (as suggested in the HTTP/1.0 status).

number	text	description
100	Continue	the client must keep on waiting for the real reply and must send reminders of its request to the server. The server says that it has understood the query but it has not the answer yet.
101	Switching Protocols	the server is going to reply with another version of HTTP

2xx - Success

These status are used when the request has been correctly recieved, understood and accepted.

numéro	texte	description
200	OK	the query is fulfiled
201	Created	a new URI has been created
202	Accepted	request accepted but not treated
203	Non-Authoritative Information	meta data sent in the header of the entity do not really correspond to the requested resource. They come from a third part. This status must be used only if there is no other solution than 200 OK.
204	No Content	request fulfiled but the server has nothing special to send
205	Reset Content	the client must refresh the currently displayed page because the server has just finished the treatment and therefore the content has changed. The reply cannot contain any entity.
206	Partial Content	the server has partially reply to the GET request

3xx - Redirection

These status are used when another request must be done for the server to complete the first request.

numéro	texte	description
300	Multiple Choices	The requested resource exists under several forms (the server has both index.htm and index.html files)
301	Moved Permanently	the resource has permanently changed location. The Location: directive then contains the new URI for the resource and the client make another request (5 times macimum) to this new URI
302	Moved Temporarily	The resource exists but is temporarily unavailable (moved). An alternate solution may be suggested.
303	See Other	the reply to the request can be found at another URI and should be obtained with a new GET request for the new URI
304	Not Modified	code sent when the client has performed a conditional `GET` and the requested document has not been updated since the given date
305	Use Proxy	the requested resource must be accessed using the given gateway
306	(Unused)	this status is reserved (was first used in a draft of the RFC2616)
307	Temporary Redirect	the requested resource is temporarily located at another URI

4xx - Client Error

The query is syntaxically wrong or misunderstood. The client has apparently commited an error in the request.

numéro	texte	description
400	Bad Request	the query is syntaxically wrong
401	Unauthorized	the user must be authenticated to access the resource. A WWW-Authenticate: directive is then sent to ask for an authentication.
402	Payment Required	reserved for a future use
403	Forbidden	the server does not want to deliver the resource. It is not an authentication failure.
404	Not Found	the requested resource cannot be found (mistake in the URI?)
405	Method Not Allowed	the client tries to use a method that is forbidden for the requested URI. The server then sends a Allow: directive to say what methods are allowed.
406	Not Acceptable	the replied entity does not correspond to the characteristics of the Accept: directive of the query's header
407	Proxy Authentication Required	the same as 401, but it precises that the client must first authenticate to the proxy
408	Request Timeout	the client did not send any query during the period of time the server was waiting
409	Conflict	there is a conflict between the request and the actual state of the resource. The client should be able to solve the problem.
410	Gone	the resource is no longer available on the server and no alternate URI has been given
411	Length Required	the query must contain a Content-Length: directive
412	Precondition Failed	one of the preconditions provided in the request's header has returned a negative result at the server-side
413	Request Entity Too Large	the requested resource is bigger than what the server can handle
414	Request-URI Too Long	the URI of the requested resource is too long. This error happens for instance when a client has made when converting a POST query to a GET one.
415	Unsupported Media Type	the media type of the requested entity is not supported by the requested resource for the requested method
416	Requested Range Not Satisfiable	the client asks for a range of the entity that cannot be determined on the resource
417	Expectation Failed	the resource expectation expressed in the Expect: directive cannot be satisfied

5xx - Server Error

The request seems to be correct, but it cannot be satisfied.

numéro	texte	description
500	Internal Server Error	the server has a problem
501	Not Implemented	the server does not implement the method used in the query
502	Bad Gateway	we are dealing with a proxy or a gateway and it does not understand the response
503	Service Unavailable	the server cannot give an answer yet for a temporary reason. The server should be able to reply later.
504	Gateway Timeout	the proxy or gateway did not recieved any reply as expected
505	HTTP Version Not Supported	the server does not support the requested HTTP version. The server should say why this version is not supported and which version it supports.

printable format