PowerShell/Data/http-status-codes.csv

1	StatusCode	Type	ShortDescription	LongDescription
2	100	Informational	Continue	The initial part of a request has been received and has not yet been rejected by the server. The server intends to send a final response after the request has been fully received and acted upon.
3	101	Informational	Switching Protocols	The server understands and is willing to comply with the client's request, via the Upgrade header field1, for a change in the application protocol being used on this connection.
4	102	Informational	Processing	An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.
5	200	Success	OK	The request has succeeded.
6	201	Success	Created	The request has been fulfilled and has resulted in one or more new resources being created.
7	202	Success	Accepted	The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
8	203	Success	Non-authoritative Information	The request was successful but the enclosed payload has been modified from that of the origin server's 200 OK response by a transforming proxy1.
9	204	Success	No Content	The server has successfully fulfilled the request and that there is no additional content to send in the response payload body.
10	205	Success	Reset Content	The server has fulfilled the request and desires that the user agent reset the "document view", which caused the request to be sent, to its original state as received from the origin server.
11	206	Success	Partial Content	The server is successfully fulfilling a range request for the target resource by transferring one or more parts of the selected representation that correspond to the satisfiable ranges found in the request's Range header field1.
12	207	Success	Multi-Status	A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate.
13	208	Success	Already Reported	Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.
14	226	Success	IM Used	The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
15	300	Redirection	Multiple Choices	The target resource has more than one representation, each with its own more specific identifier, and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to one or more of those identifiers.
16	301	Redirection	Moved Permanently	The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.
17	302	Redirection	Found	The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client ought to continue to use the effective request URI for future requests.
18	303	Redirection	See Other	The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request.
19	304	Redirection	Not Modified	A conditional GET or HEAD request has been received and would have resulted in a 200 OK response if it were not for the fact that the condition evaluated to false.
20	305	Redirection	Use Proxy	Defined in a previous version of this specification and is now deprecated, due to security concerns regarding in-band configuration of a proxy.
21	307	Redirection	Temporary Redirect	The target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI.
22	308	Redirection	Permanent Redirect	The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.
23	400	Client Error	Bad Request	The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
24	401	Client Error	Unauthorized	The request has not been applied because it lacks valid authentication credentials for the target resource.
25	402	Client Error	Payment Required	Reserved for future use.
26	403	Client Error	Forbidden	The server understood the request but refuses to authorize it.
27	404	Client Error	Not Found	The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
28	405	Client Error	Method Not Allowed	The method received in the request-line is known by the origin server but not supported by the target resource.
29	406	Client Error	Not Acceptable	The target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request1, and the server is unwilling to supply a default representation.
30	407	Client Error	Proxy Authentication Required	Similar to 401 Unauthorized, but it indicates that the client needs to authenticate itself in order to use a proxy.
31	408	Client Error	Request Timeout	The server did not receive a complete request message within the time that it was prepared to wait.
32	409	Client Error	Conflict	The request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request.
33	410	Client Error	Gone	The target resource is no longer available at the origin server and that this condition is likely to be permanent.
34	411	Client Error	Length Required	The server refuses to accept the request without a defined Content-Length1.
35	412	Client Error	Precondition Failed	One or more conditions given in the request header fields evaluated to false when tested on the server.
36	413	Client Error	Payload Too Large	The server is refusing to process a request because the request payload is larger than the server is willing or able to process.
37	414	Client Error	Request-URI Too Long	The server is refusing to service the request because the request-target1 is longer than the server is willing to interpret.
38	415	Client Error	Unsupported Media Type	The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.
39	416	Client Error	Requested Range Not Satisfiable	None of the ranges in the request's Range header field1 overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid ranges or an excessive request of small or overlapping ranges.
40	417	Client Error	Expectation Failed	The expectation given in the request's Expect header field1 could not be met by at least one of the inbound servers.
41	418	Client Error	I'm a teapot	Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.
42	421	Client Error	Misdirected Request	The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
43	422	Client Error	Unprocessable Entity	The server understands the content type of the request entity (hence a 415 Unsupported Media Type status code is inappropriate), and the syntax of the request entity is correct (thus a 400 Bad Request status code is inappropriate) but was unable to process the contained instructions.
44	423	Client Error	Locked	The source or destination resource of a method is locked.
45	424	Client Error	Failed Dependency	The method could not be performed on the resource because the requested action depended on another action and that action failed.
46	426	Client Error	Upgrade Required	The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.
47	428	Client Error	Precondition Required	The origin server requires the request to be conditional.
48	429	Client Error	Too Many Requests	The user has sent too many requests in a given amount of time ("rate limiting").
49	431	Client Error	Request Header Fields Too Large	The server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields.
50	444	Client Error	Connection Closed Without Response	A non-standard status code used to instruct nginx to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.
51	451	Client Error	Unavailable For Legal Reasons	The server is denying access to the resource as a consequence of a legal demand.
52	499	Client Error	Client Closed Request	A non-standard status code introduced by nginx for the case when a client closes the connection while nginx is processing the request.
53	500	Server Error	Internal Server Error	The server encountered an unexpected condition that prevented it from fulfilling the request.
54	501	Server Error	Not Implemented	The server does not support the functionality required to fulfill the request.
55	502	Server Error	Bad Gateway	The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
56	503	Server Error	Service Unavailable	The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.
57	504	Server Error	Gateway Timeout	The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.
58	505	Server Error	HTTP Version Not Supported	The server does not support, or refuses to support, the major version of HTTP that was used in the request message.
59	506	Server Error	Variant Also Negotiates	The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
60	507	Server Error	Insufficient Storage	The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
61	508	Server Error	Loop Detected	The server terminated an operation because it encountered an infinite loop while processing a request with "Depth: infinity". This status indicates that the entire operation failed.
62	510	Server Error	Not Extended	The policy for accessing the resource has not been met in the request. The server should send back all the information necessary for the client to issue an extended request.
63	511	Server Error	Network Authentication Required	The client needs to authenticate to gain network access.
64	599	Server Error	Network Connect Timeout Error	This status code is not specified in any RFCs, but is used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.