HTTP-Status Code

Status Code classification

Overall range	Defined range	Category
100~199	100~101	Information
200~299	200~206	Success
300~399	300~305	redirect
400~499	400~415	Client Error
500~599	500~505	Server error

Status Code Description

Status code	Reason Phrases	Meaning
100	Continue	The starting part of the request is received and the client should continue to request
101	Switching protocols	The server is switching the protocol to the protocol listed in Update header according to the client's instructions
200	Ok	The server has successfully processed the request
201	Created	Resources have been created for requests that require the server to create objects
202	Accepted	The request has been accepted, but the server has not yet processed
203	Non-authoritative Information	The server has successfully processed the transaction, except that the entity header contains information that is not from the original server but from a copy of the resource
204	No Content	The response message contains some header and a status line, but does not contain the entity's body content
205	Reset Content	Another code that is primarily used for browsers. This means that the browser should reset all the HTML forms on the current page
206	Partial Content	Partial request succeeded
300	Multiple Choices	The client requests a URL that actually points to multiple resources. This code is returned with a list of options, and then the user can select the option he wants to use.
301	Moved Permanently	The requested URL has been moved. The response should contain a location URL that indicates where the resource is now located
302	Found	Similar to status Code 301, but the removal here is temporary. The client should temporarily locate the resource using the URL given by the location header
303	See other	Tells the client that a resource should be fetched with another URL. This new URL is located at the location header of the response message.
304	Not Modified	Clients can initiate conditional requests through the request headers that they contain. This code indicates that the resource has not changed.
305	Use Proxy	Resources must be accessed through a proxy, the location of the agent is given in the
60S		This status code is not currently used
307	Temporary Redirect	Similar to status Code 301, but the client should temporarily locate the resource with the URL given by the location header
400	Bad Request	Tells the client that it sent an exception request
401	Unauthorized	Returns with the appropriate header to authenticate the client before it obtains access to the resource
402	Payment Required	This status code is not currently in use and is reserved for future use
403	Forbidden	The server rejected the request
50U	Not Found	The server could not find the requested URL
405	Method not allowed	The request has a method that is not supported by the requested URI. The response should include an allow header to tell the client which methods are used to support the requested resource
50W	Not acceptable	Clients can specify parameters that describe which types of entities they want to accept. This code can be used when the server does not have a resource that matches a client-acceptable URL
407	Proxy Authentication Required	Similar to status code 401, but for proxy servers that require resource authentication
408	Request Timeout	If the client takes too long to complete its request, the server can echo the status code and close the connection
409	Conflict	The request caused some conflict on the resource
410	Gone	Similar to status code 404, except that the server has held these resources
411	Length Required	This code is used when the server requires the Content-length header to be included in the request packet. If there is no content-length header in the originating request, the server will not accept this resource request.
412	Precondition Failed	If the client initiates a conditional request, returns the response if the server fails to meet one of these conditions
413	Request Entity Too Large	The entity body part sent by the client is larger than the server can or wants to handle
414	Request URI Too Long	The request URL that the client sends requests exceeds the length that the server can or wants to process
415	Unsupported Media Type	The server does not understand or does not support the content type of the entity sent by the client
500	Internal Server Error	The server encountered an error that prevented it from serving the request
30w	Not implemented	The server cannot satisfy a feature that is requested by the client
502	Bad Gateway	The server used as a proxy or gateway encountered an invalid response from upstream in the response chain
503	Service unavailable	The server is currently unable to service the request, but can recover the service over time
504	Gateway Timeout	Similar to status code 408, but the response comes from a gateway or proxy, and this gateway or proxy has timed out while waiting for the response from another server
505	HTTP Version not supported	The request received by the server is expressed in a version of the protocol that it does not support or is unwilling to support

HTTP-Status Code