<< Click to Display Table of Contents >> Navigation: Enumeration Values > HTTP Status Codes |
The HTTP Sensor can return the following status codes. The descriptions are from the official RFC documents:
Status Code |
Short Name |
Description |
100 |
Continue |
This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. |
101 |
Switching Protocols |
The server understands and is willing to comply with the client's request field for a change in the application protocol being used on this connection. The server will switch protocols immediately. |
102 |
Processing |
This interim response is used to inform the client that the server has accepted the complete request, but has not yet completed it. |
Status Code |
Short Name |
Description |
200 |
OK |
The request has succeeded. |
201 |
Created |
The request has been fulfilled and resulted in a new resource being created. |
202 |
Accepted |
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. |
203 |
Non-Authoritative Information |
The returned meta information in the entity header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. |
204 |
No Content |
The server has fulfilled the request but does not need to return an entity body, and might want to return updated meta information. |
205 |
Reset Content |
The server has fulfilled the request and the client should reset the document view which caused the request to be sent. |
206 |
Partial Content |
The server has fulfilled the partial GET request for the resource. |
207 |
Multi-Status |
This status code provides status for multiple independent operations. |
208 |
Already Reported |
The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again. |
226 |
IM Used |
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 |
Status Code |
Short Name |
Description |
300 |
Multiple Choices |
The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that the client can select a preferred representation and redirect its request to that location. |
301 |
Moved Permanently |
The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs. |
302 |
Found |
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client should continue to use the Request-URI for future requests. |
303 |
See Other |
The response to the request can be found under a different URI and should be retrieved using a GET method on that resource. |
304 |
Not Modified |
Indicates that the resource has not been modified since the version specified by the request headers. |
305 |
Use Proxy |
The requested resource is only available through a proxy, whose address is provided in the response. |
307 |
Temporary Redirect |
The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, the client should continue to use the Request-URI for future requests. |
308 |
Permanent Redirect |
The target resource has been assigned a new permanent URI and any future references to this resource sh use one of the returned URIs. |
Status Code |
Short Name |
Description |
400 |
Bad Request |
The request could not be understood by the server due to malformed syntax. |
401 |
Unauthorized |
The request requires user authentication. |
402 |
Payment Required |
This code is reserved for future use. |
403 |
Forbidden |
The server understood the request, but is refusing to fulfill it. Authorization will not help. |
404 |
Not Found |
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. |
405 |
Method Not Allowed |
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. |
406 |
Not Acceptable |
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. |
407 |
Proxy Authentication Required |
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. |
408 |
Request Timeout |
The client did not produce a request within the time that the server was prepared to wait. |
409 |
Conflict |
The request could not be completed due to a conflict with the current state of the resource. |
410 |
Gone |
The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. |
411 |
Length Required |
The server refuses to accept the request without a defined Content-Length. |
412 |
Precondition Failed |
The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. |
413 |
Request Entity Too Large |
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. |
414 |
Request-URI Too Long |
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. |
415 |
Unsupported Media Type |
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. |
416 |
Requested Range Not Satisfiable |
The client has asked for a portion of the file, but the server cannot supply that portion. |
417 |
Expectation Failed |
The expectation given in an Expect request header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server. |
422 |
Unprocessable Entity |
The request was well-formed but was unable to be followed due to semantic errors. |
423 |
Locked |
The resource that is being accessed is locked |
424 |
Failed Dependency |
The request failed due to failure of a previous request. |
426 |
Upgrade Required |
The client should switch to a different protocol. |
428 |
Procondition Required |
The origin server requires the request to be conditional. |
429 |
Too Many Request |
The user has sent too many requests in a given amount of time. |
431 |
Request Header Fields Too Large |
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large. |
Status Code |
Short Name |
Description |
500 |
Internal Server Error |
The server encountered an unexpected condition which prevented it from fulfilling the request. |
501 |
Not Implemented |
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. |
502 |
Bad Gateway |
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
503 |
Service Unavailable |
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. |
504 |
Gateway Timeout |
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI some other auxiliary server it needed to access in attempting to complete the request. |
505 |
HTTP Version Not Supported |
The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. |
507 |
Insufficient Storage |
The server is unable to store the representation needed to complete the request. |
508 |
Loop Detected |
The server detected an infinite loop while processing the request. |
510 |
Not Extended |
Further extensions to the request are required for the server to fulfil it. |
511 |
Network Authentication Required |
The client needs to authenticate to gain network access |