TSV

HTTP Status Codes - TSV

HTTP status codes are three-digit numeric codes returned by web servers in response to client requests, indicating the result of request processing. Defined in a registry managed by IANA (Internet Assigned Numbers Authority), they are categorized into five classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). These codes are essential elements in web development and API design, utilized for proper error handling and debugging.

HTTP Web Internet protocol status code RFC
code	slug	name	description	category	reference
100	continue	Continue	Indicates that the initial part of a request has been received and the client should continue.	1xx Informational	RFC 9110, Section 15.2.1
101	switching-protocols	Switching Protocols	Indicates that the server agrees to switch protocols.	1xx Informational	RFC 9110, Section 15.2.2
102	processing	Processing	Indicates that the server has received and is processing the request.	1xx Informational	RFC 2518
103	early-hints	Early Hints	Used to send some response headers before the final response.	1xx Informational	RFC 8297
104	upload-resumption-supported	Upload Resumption Supported	Indicates that the server supports upload resumption (temporary registration).	1xx Informational	draft-ietf-httpbis-resumable-upload-05
200	ok	OK	Standard response for successful HTTP requests.	2xx Success	RFC 9110, Section 15.3.1
201	created	Created	Request has been fulfilled and resulted in a new resource being created.	2xx Success	RFC 9110, Section 15.3.2
202	accepted	Accepted	Request has been accepted for processing, but processing has not been completed.	2xx Success	RFC 9110, Section 15.3.3
203	non-authoritative-information	Non-Authoritative Information	Indicates that the returned metadata is not from the origin server.	2xx Success	RFC 9110, Section 15.3.4
204	no-content	No Content	Server successfully processed the request but is not returning any content.	2xx Success	RFC 9110, Section 15.3.5
205	reset-content	Reset Content	Indicates that the client should reset the document view.	2xx Success	RFC 9110, Section 15.3.6
206	partial-content	Partial Content	Indicates that the server is delivering only part of the resource.	2xx Success	RFC 9110, Section 15.3.7
207	multi-status	Multi-Status	Response containing multiple status codes for multiple resources.	2xx Success	RFC 4918
208	already-reported	Already Reported	Indicates that DAV binding members have already been enumerated.	2xx Success	RFC 5842
226	im-used	IM Used	Indicates that the server fulfilled a GET request and instance manipulations were applied.	2xx Success	RFC 3229
300	multiple-choices	Multiple Choices	Indicates that there are multiple options for the resource.	3xx Redirection	RFC 9110, Section 15.4.1
301	moved-permanently	Moved Permanently	Indicates that the resource has been permanently moved to a new URI.	3xx Redirection	RFC 9110, Section 15.4.2
302	found	Found	Indicates that the resource temporarily resides under a different URI.	3xx Redirection	RFC 9110, Section 15.4.3
303	see-other	See Other	Indicates that the response can be found under a different URI.	3xx Redirection	RFC 9110, Section 15.4.4
304	not-modified	Not Modified	Indicates that the resource has not been modified since the last request.	3xx Redirection	RFC 9110, Section 15.4.5
305	use-proxy	Use Proxy	Requested resource must be accessed through a proxy.	3xx Redirection	RFC 9110, Section 15.4.6
306	unused	(Unused)	This status code is no longer used.	3xx Redirection	RFC 9110, Section 15.4.7
307	temporary-redirect	Temporary Redirect	Indicates that the request should be repeated with another URI.	3xx Redirection	RFC 9110, Section 15.4.8
308	permanent-redirect	Permanent Redirect	Indicates that the resource has been permanently moved to a new URI and request method should be preserved.	3xx Redirection	RFC 9110, Section 15.4.9
400	bad-request	Bad Request	Indicates that the server cannot understand the request due to malformed syntax.	4xx Client Error	RFC 9110, Section 15.5.1
401	unauthorized	Unauthorized	Indicates that authentication is required to access the resource.	4xx Client Error	RFC 9110, Section 15.5.2
402	payment-required	Payment Required	Status code reserved for future use.	4xx Client Error	RFC 9110, Section 15.5.3
403	forbidden	Forbidden	Indicates that the server refuses to fulfill the request.	4xx Client Error	RFC 9110, Section 15.5.4
404	not-found	Not Found	Indicates that the server cannot find the requested resource.	4xx Client Error	RFC 9110, Section 15.5.5
405	method-not-allowed	Method Not Allowed	Indicates that the request method is not supported for the target resource.	4xx Client Error	RFC 9110, Section 15.5.6
406	not-acceptable	Not Acceptable	Indicates that no content satisfying the request's Accept headers is available.	4xx Client Error	RFC 9110, Section 15.5.7
407	proxy-authentication-required	Proxy Authentication Required	Indicates that the client must authenticate with a proxy.	4xx Client Error	RFC 9110, Section 15.5.8
408	request-timeout	Request Timeout	Indicates that the server timed out waiting for a request from the client.	4xx Client Error	RFC 9110, Section 15.5.9
409	conflict	Conflict	Indicates that the request conflicts with the current state of the resource.	4xx Client Error	RFC 9110, Section 15.5.10
410	gone	Gone	Indicates that the requested resource is no longer available and will not be available again.	4xx Client Error	RFC 9110, Section 15.5.11
411	length-required	Length Required	Indicates that the request requires a Content-Length header.	4xx Client Error	RFC 9110, Section 15.5.12
412	precondition-failed	Precondition Failed	Indicates that a precondition in the request headers was not met.	4xx Client Error	RFC 9110, Section 15.5.13
413	content-too-large	Content Too Large	Indicates that the request entity is larger than the server is willing to process.	4xx Client Error	RFC 9110, Section 15.5.14
414	uri-too-long	URI Too Long	Indicates that the request URI is longer than the server is willing to interpret.	4xx Client Error	RFC 9110, Section 15.5.15
415	unsupported-media-type	Unsupported Media Type	Indicates that the request media type is not supported by the server.	4xx Client Error	RFC 9110, Section 15.5.16
416	range-not-satisfiable	Range Not Satisfiable	Indicates that the range specified in the request's Range header cannot be fulfilled.	4xx Client Error	RFC 9110, Section 15.5.17
417	expectation-failed	Expectation Failed	Indicates that the server cannot meet the requirements of the Expect header.	4xx Client Error	RFC 9110, Section 15.5.18
418	im-a-teapot	(Unused)	This status code is no longer used.	4xx Client Error	RFC 9110, Section 15.5.19
421	misdirected-request	Misdirected Request	Indicates that the request was directed at a server unable to produce a response.	4xx Client Error	RFC 9110, Section 15.5.20
422	unprocessable-content	Unprocessable Content	Indicates that the request is syntactically correct but has semantic errors.	4xx Client Error	RFC 9110, Section 15.5.21
423	locked	Locked	Indicates that the resource is locked and cannot be accessed.	4xx Client Error	RFC 4918
424	failed-dependency	Failed Dependency	Indicates that the request failed due to failure of a previous request.	4xx Client Error	RFC 4918
425	too-early	Too Early	Indicates that the server is unwilling to risk processing a request that might be replayed.	4xx Client Error	RFC 8470
426	upgrade-required	Upgrade Required	Indicates that the client should switch to a different protocol.	4xx Client Error	RFC 9110, Section 15.5.22
428	precondition-required	Precondition Required	Indicates that the server requires the request to be conditional.	4xx Client Error	RFC 6585
429	too-many-requests	Too Many Requests	Indicates that the user has sent too many requests in a given time period.	4xx Client Error	RFC 6585
431	request-header-fields-too-large	Request Header Fields Too Large	Indicates that the request header fields are too large.	4xx Client Error	RFC 6585
451	unavailable-for-legal-reasons	Unavailable For Legal Reasons	Indicates that the resource is unavailable due to legal reasons.	4xx Client Error	RFC 7725
500	internal-server-error	Internal Server Error	Indicates that an unexpected error occurred on the server.	5xx Server Error	RFC 9110, Section 15.6.1
501	not-implemented	Not Implemented	Indicates that the server does not support the request method.	5xx Server Error	RFC 9110, Section 15.6.2
502	bad-gateway	Bad Gateway	Indicates that the server received an invalid response while acting as a gateway.	5xx Server Error	RFC 9110, Section 15.6.3
503	service-unavailable	Service Unavailable	Indicates that the server is temporarily unable to handle the request.	5xx Server Error	RFC 9110, Section 15.6.4
504	gateway-timeout	Gateway Timeout	Indicates that the gateway did not receive a timely response from an upstream server.	5xx Server Error	RFC 9110, Section 15.6.5
505	http-version-not-supported	HTTP Version Not Supported	Indicates that the server does not support the HTTP version used in the request.	5xx Server Error	RFC 9110, Section 15.6.6
506	variant-also-negotiates	Variant Also Negotiates	Indicates that the server has an internal configuration error.	5xx Server Error	RFC 2295
507	insufficient-storage	Insufficient Storage	Indicates that the server has insufficient storage to complete the request.	5xx Server Error	RFC 4918
508	loop-detected	Loop Detected	Indicates that the server detected an infinite loop while processing a request.	5xx Server Error	RFC 5842
510	not-extended	Not Extended (OBSOLETED)	Indicates that further extensions to the request are required (obsoleted).	5xx Server Error	RFC 2774
511	network-authentication-required	Network Authentication Required	Indicates that the client needs to authenticate to gain network access.	5xx Server Error	RFC 6585