Check Remote Server Status

This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished.

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.

This code is sent in response to an Upgrade request header by the client, and indicates the protocol the server is switching too.

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.

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

An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.

The request has succeeded. The payload sent in a 200 response depends on the request method.

The meaning of a success varies depending on the HTTP method:

• GET: The resource has been fetched and is transmitted in the message body.
• HEAD: The entity headers are in the message body.
• POST: The resource describing the result of the action is transmitted in the message body.
• TRACE: The message body contains the request message as received by the server

The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request.

The primary resource created by the request is identified by either a Location header field in the response or, if no Location field is received, by the effective request URI.

The request was successful but the enclosed payload has been modified from that of the origin server's 200 OK response by a transforming proxy.

This response code means returned meta-information set is not exact set as available from the origin server, but collected from a local or a third party copy.

There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones.

The server has successfully fulfilled the request and that there is no additional content to send in the response payload body.

This response code is sent after accomplishing request to tell user agent reset document view which sent this request.

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.

This response code is used because of range header sent by the client to separate download into multiple streams.

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 field

A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate.

The default Multi-Status response body is a text/xml or application/xml HTTP entity with a 'multistatus' root element. Further elements contain 200, 300, 400, and 500 series status codes generated during the method invocation.

Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.

For each binding to a collection inside the request's scope, only one will be reported with a 200 status, while subsequent DAV:response elements for all other bindings will use the 208 status, and no DAV:response elements for their descendants are included.

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.

The actual current instance might not be available except by combining this response with other previous or future responses, as appropriate for the specific instance-manipulation(s).

The request has more than one possible responses. User-agent or user should choose one of them. There is no standardized way to choose one of the responses.

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.

This response code means that URI of requested resource has been changed. Probably, new URI would be given in the response.

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.

This response code means that URI of requested resource has been changed temporarily. New changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.

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.

Server sent this response to directing client to get requested resource to another URI with an GET request.

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.

This is used for caching purposes. It is telling to client that response has not been modified. So, client can continue to use same cached version of response.

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.

Was defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.

Server sent this response to directing client to get requested resource to another URI with same method that used prior request. This has the same semantic than the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

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.

This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

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.

This response means that server could not understand the request due to invalid syntax.

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).

The request has not been applied because it lacks valid authentication credentials for the target resource.

Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

This response code is reserved for future use. Initial aim for creating this code was using it for digital payment systems however this is not used currently.

Reserved for future use.

The server understood the request but refuses to authorize it.

The client does not have access rights to the content, i.e. they are unauthorized, so server is rejecting to give proper response. Unlike 401, the client's identity is known to the server.

The server can not find requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist.

Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurence on the web.

The method received in the request-line is known by the origin server but not supported by the target resource.

The request method is known by the server but has been disabled and cannot be used. For example, an API may forbid DELETE-ing a resource. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code.

This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content following the criteria given by the user agent.

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 request, and the server is unwilling to supply a default representation.

Similar to 401 Unauthorized, but it indicates that the client needs to authenticate itself in order to use a proxy.

This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection.

This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.

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.

This response is sent when a request conflicts with the current state of the server.

This response would be sent when the requested content has been permenantly deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource.

The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code.

The server refuses to accept the request without a defined Content-Length.

Server rejected the request because the Content-Length header field is not defined and the server requires it.

The client has indicated preconditions in its headers which the server does not meet.

One or more conditions given in the request header fields evaluated to false when tested on the server.

The server is refusing to process a request because the request payload is larger than the server is willing or able to process.

Request entity is larger than limits defined by server; the server might close the connection or return an Retry-After header field.

The URI requested by the client is longer than the server is willing to interpret.

The server is refusing to service the request because the request-target is longer than the server is willing to interpret.

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.

The media format of the requested data is not supported by the server, so the server is rejecting the request.

The range specified by the Range header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.

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.

The expectation given in the request's Expect header field could not be met by at least one of the inbound servers.

This response code means the expectation indicated by the Expect request header field can't be met by the server.

The server refuses the attempt to brew coffee with 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.

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.

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

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.

The source or destination resource of a method is locked.

The request failed due to failure of a previous request.

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

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.

The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.

The user has sent too many requests in a given amount of time ("rate limiting").

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.

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.

The user requests an illegal resource, such as a web page censored by a government.

The server is denying access to the resource as a consequence of a legal demand.

A non-standard status code introduced by nginx for the case when a client closes the connection while nginx is processing the request.

The server has encountered a situation it doesn't know how to handle.

The server encountered an unexpected condition that prevented it from fulfilling the request.

The server does not support the functionality required to fulfill the request.

The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD.

This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.

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.

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.

The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

This error response is given when the server is acting as a gateway and cannot get a response in time.

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.

The server does not support, or refuses to support, the major version of HTTP that was used in the request message.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error: transparent content negotiation for the request results in a circular reference.

Is therefore not a proper end point in the negotiation process

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

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.

The server detected an infinite loop while processing the request.

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.

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.

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

The 511 status code indicates that the client needs to authenticate to gain network access.

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.