63 results found
63 status codes
100ContinueThe server has received the request headers and the client should proceed to send the request body.
101Switching ProtocolsThe server is switching protocols as requested by the client via the Upgrade header.
102ProcessingThe server has received and is processing the request, but no response is available yet.
103Early HintsUsed to return some response headers before the final HTTP message, allowing the client to preload resources.
200OKThe request has succeeded. The meaning of the success depends on the HTTP method used.
201CreatedThe request has been fulfilled and a new resource has been created.
202AcceptedThe request has been accepted for processing, but the processing has not been completed.
203Non-Authoritative InformationThe returned meta-information is from a local or third-party copy, not the origin server.
204No ContentThe server has fulfilled the request but does not need to return an entity-body.
205Reset ContentThe server has fulfilled the request and the user agent should reset the document view.
206Partial ContentThe server has fulfilled the partial GET request for the resource.
207Multi-StatusConveys information about multiple resources in situations where multiple status codes might be appropriate.
208Already ReportedUsed in DAV binding to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.
226IM UsedThe server has fulfilled a GET request for the resource, and the response represents the result of instance-manipulations.
300Multiple ChoicesThe target resource has more than one representation, each with its own URI.
301Moved PermanentlyThe target resource has been assigned a new permanent URI; future references should use one of the enclosed URIs.
302FoundThe target resource resides temporarily under a different URI. The user agent should not change the stored URI for future requests.
303See OtherThe server is redirecting the user agent to a different resource via a GET request.
304Not ModifiedIndicates that the resource has not been modified since the version specified by the request headers.
305Use ProxyThe requested resource must be accessed through the proxy given by the Location field.
306(Unused)This status code is no longer used but is reserved for future use.
307Temporary RedirectThe target resource resides temporarily under a different URI; the user agent must not change the request method if it performs an automatic redirect.
308Permanent RedirectThe target resource has been assigned a new permanent URI; the user agent must not change the request method if it performs an automatic redirect.
400Bad RequestThe server cannot process the request due to something that is perceived to be a client error.
401UnauthorizedThe request requires user authentication. The response must include a WWW-Authenticate header field.
402Payment RequiredReserved for future use, intended for digital payment systems.
403ForbiddenThe server understood the request but refuses to authorize it.
404Not FoundThe origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
405Method Not AllowedThe method received in the request-line is not supported by the target resource.
406Not AcceptableThe target resource does not have a representation acceptable according to the Accept headers sent in the request.
407Proxy Authentication RequiredThe client must first authenticate itself with the proxy.
408Request TimeoutThe server did not receive a complete request message within the time it was prepared to wait.
409ConflictThe request could not be completed due to a conflict with the current state of the target resource.
410GoneThe target resource is no longer available at the origin server and no forwarding address is known.
411Length RequiredThe server refuses to accept the request without a defined Content-Length.
412Precondition FailedOne or more conditions given in the request header fields evaluated to false when tested on the server.
413Content Too LargeThe request payload is larger than the server is willing or able to process.
414URI Too LongThe request-target is longer than the server is willing to interpret.
415Unsupported Media TypeThe origin server refuses the request because the payload is in a format not supported by the target resource.
416Range Not SatisfiableNone of the ranges in the Range header field overlap the current extent of the selected resource.
417Expectation FailedThe expectation given in the Expect header field could not be met by the server.
418I'm a TeapotThe server refuses to brew coffee because it is, permanently, a teapot. A humorous status code defined by RFC 2324.
421Misdirected RequestThe request was directed at a server that is not able to produce a response.
422Unprocessable ContentThe server understands the content type and syntax of the request but was unable to process the contained instructions.
423LockedThe source or destination resource of a method is locked.
424Failed DependencyThe method could not be performed because the requested action depended on another action that failed.
425Too EarlyThe server is unwilling to risk processing a request that might be replayed.
426Upgrade RequiredThe server refuses to perform the request using the current protocol but may do so after the client upgrades.
428Precondition RequiredThe origin server requires the request to be conditional to prevent the lost update problem.
429Too Many RequestsThe user has sent too many requests in a given amount of time (rate limiting).
431Request Header Fields Too LargeThe server is unwilling to process the request because its header fields are too large.
451Unavailable For Legal ReasonsThe server is denying access to the resource as a consequence of a legal demand.
500Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
501Not ImplementedThe server does not support the functionality required to fulfill the request.
502Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from an inbound server.
503Service UnavailableThe server is currently unable to handle the request due to temporary overloading or maintenance.
504Gateway TimeoutThe server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
505HTTP Version Not SupportedThe server does not support the major version of HTTP that was used in the request message.
506Variant Also NegotiatesTransparent content negotiation for the request results in a circular reference.
507Insufficient StorageThe method could not be performed on the resource because the server is unable to store the representation.
508Loop DetectedThe server detected an infinite loop while processing the request.
510Not ExtendedFurther extensions to the request are required for the server to fulfill it.
511Network Authentication RequiredThe client needs to authenticate to gain network access.