HTTPStatusCode

The response class representation of status codes, these get grouped by their first digit.

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

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

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

• ok: Standard response for successful HTTP requests.

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

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

• nonAuthoritativeInformation: 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.

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

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

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

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

• alreadyReported: The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again.

• IMUsed: 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.

• multipleChoices: Indicates multiple options for the resource from which the client may choose

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

• found: The resource was found.

• seeOther: The response to the request can be found under another URI using a GET method.

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

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

• switchProxy: No longer used. Originally meant “Subsequent requests should use the specified proxy.

• temporaryRedirect: The request should be repeated with another URI.

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

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

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

• paymentRequired: The content available on the server requires payment.

• forbidden: The request was a valid request, but the server is refusing to respond to it.

• notFound: The requested resource could not be found but may be available in the future.

• methodNotAllowed: A request method is not supported for the requested resource. e.g. a GET request on a form which requires data to be presented via POST

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

• proxyAuthenticationRequired: The client must first authenticate itself with the proxy.

• requestTimeout: The server timed out waiting for the request.

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

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

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

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

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

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

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

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

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

• teapot: This HTTP status is used as an Easter egg in some websites.

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

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

• locked: The resource that is being accessed is locked.

• failedDependency: The request failed due to failure of a previous request (e.g., a PROPPATCH).

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

• preconditionRequired: The origin server requires the request to be conditional.

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

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

• noResponse: Used to indicate that the server has returned no information to the client and closed the connection.

• unavailableForLegalReasons: 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.

• SSLCertificateError: An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.

• SSLCertificateRequired: An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.

• HTTPRequestSentToHTTPSPort: An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.

• clientClosedRequest: Used when the client has closed the request before the server could send a response.

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

• notImplemented: The server either does not recognize the request method, or it lacks the ability to fulfill the request.

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

• serviceUnavailable: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

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

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

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

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

• loopDetected: The server detected an infinite loop while processing the request.

• notExtended: Further extensions to the request are required for the server to fulfill it.

• networkAuthenticationRequired: The client needs to authenticate to gain network access.

The class (or group) which the status code belongs to.