HttpStatusCode Enum

The client request wasn't successful.

The client should continue with its request.

The HTTP protocol version or protocol is being changed.

The server has received a Web Distributed Authoring and Versioning (WebDAV) request and is processing the request.

This status code is an HTTP extension used with WebDAV. It can only be returned if the client HTTP request included the DAV header in the request. This status code is documented in IETF RFC 2518.

The request succeeded and that the requested information is in the response. This is the most common status code to receive.

The request resulted in a new resource created before the response was sent.

The request has been accepted for further processing.

The returned meta-information is from a cached copy instead of the origin server and therefore may be incorrect.

The request has been successfully processed and that the response is intentionally blank.

The client should reset (not reload) the current resource.

The response is a partial response as requested by a GET request that includes a byte range.

The response provides status for multiple independent operations. Specific error messages appear in the body of the multi- status response.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). This status code is documented in IETF RFC 4918.

Some of the results of the requested operation were already reported.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). It can only be returned if the client HTTP request included the DAV header in the request. This status code is documented in IETF RFC 5842.

The server has fulfilled a GET request for the resource and the response is the result of one or more actions applied to the current instance.

This status code is documented in IETF RFC 3229.

The requested information has multiple representations. The default action is to treat this status as a redirect and follow the contents of the Location header associated with this response.

The requested information has been moved to the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response.

The requested information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

Automatically redirects the client to the URI specified in the Location header as the result of a POST. The request to the resource specified by the Location header will be made with the GET method.

The client's cached copy is up to date. The contents of the resource are not transferred.

The request should use the proxy server at the URI specified in the Location header.

The request information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will also use the POST method.

The target resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs specified in the Location header.

This status code is documented in IETF draft draft-reschke-http-status-308.

The request could not be understood by the server. This status code is sent when no other error is applicable, or if the exact error is unknown or does not have its own error code.

The requested resource requires authentication. The WWW-Authenticate header contains the details of how to perform the authentication.

This code is reserved for future use.

The server refuses to fulfill the request.

The requested resource does not exist on the server.

The HTTP method in the request is not allowed on the requested resource.

The client has indicated with Accept headers that it will not accept any of the available representations of the resource.

The requested proxy requires authentication. The Proxy-Authenticate header contains the details of how to perform the authentication.

The client did not send a request within the time the server was expecting the request.

The request could not be carried out because of a conflict on the server.

The requested resource is no longer available.

The required Content-Length header is missing.

A condition set for this request failed, and the request cannot be carried out. Conditions are set with conditional request headers like If-Match, If-None-Match, or If-Unmodified-Since.

The request is too large for the server to process.

The URI is too long.

The request is an unsupported type.

The range of data requested from the resource cannot be returned, either because the beginning of the range is before the beginning of the resource, or the end of the range is after the end of the resource.

An expectation given in an Expect header could not be met by the server.

The server understands the content type of the request entity and the syntax of the request entity is correct, but the server was unable to process the contained instructions.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). This status code is documented in IETF RFC 4918.

The source or destination resource of a method is locked. This response should contain an appropriate precondition or post-condition code.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). This status code is documented in IETF RFC 4918.

The method could not be performed on the resource because the requested action depended on another action and that action failed.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). This status code is documented in IETF RFC 4918.

The client should switch to a different protocol such as TLS/1.0.

This status code is documented in IETF RFC 2917.

The origin server requires the request to be conditional.

This status code is documented in IETF RFC 6585.

The user has sent too many requests in a given amount of time. The response should include details explaining the condition, and may include a Retry-After header indicating how long to wait before making a new request.

This status code is documented in IETF RFC 6585.

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.

This status code is documented in IETF RFC 6585.

A generic error has occurred on the server.

The server does not support the requested function.

An intermediate proxy server received a bad response from another proxy or the origin server.

The server is temporarily unavailable, usually due to high load or maintenance.

An intermediate proxy server timed out while waiting for a response from another proxy or the origin server.

The requested HTTP version is not supported by the server.

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.

This status code is documented in IETF RFC 2295.

The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. This condition is considered to be temporary.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). This status code is documented in IETF RFC 4918.

The server terminated an operation because it encountered an infinite loop while processing a request. This status indicates that the entire operation failed.

This status code is an HTTP extension used with Web Distributed Authoring and Versioning (WebDAV). It can only be returned if the client HTTP request included the DAV header in the request. This status code is documented in IETF RFC 5842.

The policy for accessing the resource has not been met in the request.

This status code is documented in IETF RFC 2774.

The server indicates that the client needs to authenticate to gain network access. The response should contain a link to a resource that allows the user to submit credentials.

This status code is documented in IETF RFC 6585.