HttpStatusCodes

The request has been accepted for processing, but the processing has not been completed.

The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

The server cannot or will not process the request due to an apparent client error.

Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.

The server has received the request headers and the client should proceed to send the request body.

The request has been fulfilled, resulting in the creation of a new resource.

Used to return some response headers before final HTTP message.

The server cannot meet the requirements of the Expect request-header field.

The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).

The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.

Tells the client to look at (browse to) another url. 302 has been superseded by 303 and 307.

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

Indicates that the resource requested is no longer available and will not be available again.

The server does not support the HTTP protocol version used in the request.

The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

The server is unable to store the representation needed to complete the request.

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

The request did not specify the length of its content, which is required by the requested resource.

The resource that is being accessed is locked.

The server detected an infinite loop while processing the request.

A request method is not supported for the requested resource.

The request was directed at a server that is not able to produce a response.

This and all future requests should be directed to the given URI.

Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation).

The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

The client needs to authenticate to gain network access.

The server successfully processed the request and is not returning any content.

The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

Further extensions to the request are required for the server to fulfil it.

The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

The server either does not recognize the request method, or it lacks the ability to fulfil the request.

Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.

Standard response for successful HTTP requests.

The server is delivering only part of the resource (byte serving) due to a range header sent by the client.

The request is larger than the server is willing or able to process.

Reserved for future use.

The request and all future requests should be repeated using another URI.

The server does not meet one of the preconditions that the requester put on the request.

The origin server requires the request to be conditional.

This code indicates that the server has received and is processing the request, but no response is available yet.

The client must first authenticate itself with the proxy.

The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

The server timed out waiting for the request.

The server successfully processed the request, but is not returning any content.

The response to the request can be found under another URI using the GET method.

The server is currently unavailable (because it is overloaded or down for maintenance).

The requester has asked the server to switch protocols and the server has agreed to do so.

No longer used. Originally meant "Subsequent requests should use the specified proxy."

In this case, the request should be repeated with another URI; however, future requests should still use the original URI.

The user has sent too many requests in a given amount of time.

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.

The request was well-formed but was unable to be followed due to semantic errors.

The request entity has a media type which the server or resource does not support.

The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.

The URI provided was too long for the server to process.

The requested resource is available only through a proxy, the address for which is provided in the response.

Transparent content negotiation for the request results in a circular reference.