When a Catchpoint test makes a request to an HTTP server, it receives a response which includes a Status Code. The standard code when a request is successful is 200 OK. There are many other codes, including various error codes that can help you understand why a request failed. The tables below list the standard HTML status codes and describe the meaning of each.
1xx: Information
Message: | Description: |
100 Continue | The server has accepted the request headers, and the client may proceed to send the request body |
101 Switching Protocols | The client has asked the server to switch protocols, and the server is doing so. (Response usually also includes the protocol the server is switching to) |
103 Early Hints | The server is returning some response headers before returning the final HTTP message |
2xx: Successful
Message: | Description: |
200 OK | The request is OK (standard response for successful HTTP requests) |
201 Created | The request has been fulfilled, and the requested new resource is created |
202 Accepted | The request has been accepted for processing, but the processing is still ongoing |
203 Non-Authoritative Information | The request has been successfully processed, but is returning information that may be from another source |
204 No Content | The request has been successfully processed, but no content was returned |
205 Reset Content | The request has been successfully processed, but is not returning any content, and the server requires the requester to reset the document view to its initial state |
206 Partial Content | The server is delivering only a portion of the requested resource due to a range header specified in the request |
3xx: Redirection
Message: | Description: |
300 Multiple Choices | The request returned multiple valid responses, so the user-agent or the user must select one of them |
301 Moved Permanently | The requested page has moved to a new URL, indicated in the response Location headers |
302 Found | The requested page has moved temporarily to a new URL indicated in the Location headers |
303 See Other | The requested page can be found under a different URL indicated in the Location headers |
304 Not Modified | Indicates the requested page has not been modified since last requested, so the client may redirect to a cached resource |
307 Temporary Redirect | The requested page has moved temporarily to a new URL indicated in the Location headers |
308 Permanent Redirect | The requested page has moved permanently to a new URL. (This status code is similar to |
4xx: Client Error
Message: | Description: |
400 Bad Request | The request cannot be fulfilled due to bad syntax |
401 Unauthorized | The request was a legal request, but the server is refusing to respond to it. Typically indicates that authentication is possible but has failed or not yet been provided |
402 Payment Required | Created to support payment/digital cash transactions. This is a nonstandard response, reserved for future use. |
403 Forbidden | The server understood the request but refuses to authorize it. |
404 Not Found | The requested page could not be found but may be available again in the future |
405 Method Not Allowed | A request was made of a page using a request method not supported by that page |
406 Not Acceptable | The server can only generate a response that is not accepted by the client |
407 Proxy Authentication Required | The client must first authenticate itself with the proxy |
408 Request Timeout | The server timed out waiting for the request |
409 Conflict | The request could not be completed because of a conflict in the request |
410 Gone | The requested page is no longer available, and is not expected to return |
411 Length Required | The "Content-Length" header is not defined, and the server will not accept the request without it |
412 Precondition Failed | The precondition provided in the request evaluated to false by the server |
413 Request Too Large | The server will not accept the request because the request entity is too large |
414 Request-URI Too Long | The server will not accept the request because the URI is too long. This may occur when you convert a POST request to a GET request with a long query information |
415 Unsupported Media Type | The server will not accept the request because the media type is not supported |
416 Range Not Satisfiable | The client has asked for a portion of the file but the specified portion is not valid or cannot be supplied by the server |
417 Expectation Failed | The server cannot meet the requirements of the Expect request-header field |
5xx: Server Error
Message: | Description: |
500 Internal Server Error | A generic error message, given when no more specific message is suitable |
501 Not Implemented | The server either does not recognize the request method, or it lacks the ability to fulfill the request |
502 Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server |
503 Service Unavailable | The server is currently unavailable (overloaded or down) |
504 Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server |
505 HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request |
511 Network Authentication Required | The client needs to authenticate to gain network access |