LoadPro Error Codes
Any of these errors may be reported during a test:
400 Series Error Codes |
|
| 400: Bad Request | The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. |
| 401: Unauthorized | The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43]. |
| 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 and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. |
| 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. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable. |
| 405: Method Not Allowed | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource. |
| 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.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection. Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable. If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions. |
| 407: Proxy Authentication Required | This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43]. |
| 408: Request Timeout | The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time. |
| 409: Conflict | The request could not be
completed due to a conflict with the current state of the resource.
This code is only allowed in situations where it is expected that
the user might be able to resolve the conflict and resubmit the
request. The response body SHOULD include enough
information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type. |
| 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.
Clients with link editing capabilities SHOULD delete references to
the Request-URI after user approval. If the server does not know,
or has no facility to determine, whether or not the condition is
permanent, the status code 404 (Not Found) SHOULD be used instead.
This response is cacheable unless indicated otherwise.
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner. |
| 411: Length Required | The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message. |
| 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. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended. |
| 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. The server MAY close the
connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again. |
| 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. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI. |
| 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 | A server SHOULD return a
response with this status code if a request included a Range
request-header field (section 14.35), and none of the
range-specifier values in this field overlap the current extent of
the selected resource, and the request did not include an If-Range
request-header field. (For byte-ranges, this means that the first-
byte-pos of all of the byte-range-spec values were greater than the
current length of the selected resource.)
When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content- type. |
| 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. |
500 Series Error Codes |
|
| 500: Internal 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. If
known, the length of the delay MAY be indicated in a Retry-After
header. If no Retry-After is given, the client SHOULD handle the
response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection. |
| 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 (e.g. HTTP, FTP, LDAP) or some
other auxiliary server (e.g. DNS) it needed to access in attempting
to complete the request.
Note: Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out. |
| 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. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server. |
Keynote Defined Error Codes (600-799) |
|
| 600: CONNECTION ERROR | This indicates a general connection error |
| 601: INCOMPLETE ERROR | This indicates sever sends an incomplete page/object (as indicated by Content-Length header) |
| 602: UNEXPECTED CLOSE ERROR | This indicates socket connection has been closed unexpectedly |
| 603: REFUSED ERROR | This indicates a request to connect to the server is refused |
| 604: TIMEOUT ERROR | This indicates there is no activity in socket connection in 3 minutes |
| 605: REDIRECT ERROR | This indicates an error in redirect HTTP header |
| 606: SSL ERROR | This indicates a general error in SSL |
| 607: HEADER ERROR | This indicates a malformed HTTP header |
| 608: EMPTY RESPONSE ERROR | This indicates server doesn't send any response after a request is sent |
| 609: UNKNOWN HOST ERROR | This indicates socket receives an unknown host error from DNS |
| 610: NO ROUTE TO HOST ERROR | This indicates a no route to host error was received while attempting to open a socket |
| 611: SOCKET ERROR | This indicates a general socket error |
| 612: FRAME LOOP ERROR | This indicates a page has a frame loop (frame A includes Frame B that includes Frame A) |
| 613: REDIRECT LOOP ERROR | This indicates a page has a redirect loop (page A redirects to page B that redirects to page A) |
| 614: CONNECTION RESET ERROR | This indicates socket receive a reset signal from the server |
| 615: SOCKET PROTOCOL ERROR | This indicates an error in socket protocol |
| 616: SOCKET BIND ERROR | This indicates an error in binding the socket |
| 617: CONNECTION ERROR | This indicates a general socket connection error |
| 618: CHUNK ERROR | This indicates an error in chunked encoding |
| 619: SSL TIMEOUT | This indicates a timeout during SSL handshake (2 minutes) |
| 620: SSL END OF INPUT | This indicates an end-of-file is received during SSL handshake |
| 621: SSL HANDSHAKE ERROR | This indicates a general error during SSL handshake |
| 622: SSL CERTIFICATE ERROR | This indicates an error in SSL certificate verification |
| 623: SSL AUTHENTICATION ERROR | This indicates an authentication error during SSL handshake |
| 624: SSL BAD MAC ERROR | This indicates a bad MAC during SSL handshake |
| 625: SSL CIPHER ERROR | This indicates a cipher error during SSL handshake |
| 701: ERROR TEXT FOUND | This code is returned if any error text (such as, "Service Unavailable") are found in the main page (frame HTML contents included). Note that the error text must be defined in advance of the test. Error text means if the text is found, this session should be considered a failure. |
| 702: REQUIRED TEXT NOT FOUND | This code is returned If not all required texts are found in the main page. Note that required text must be defined in advance of the test. Required text means if the text is not found, this session should be considered a failure. |
| 703: HTML BODY EMPTY | This code is returned if the HTML body of the page is empty (only if error text or required text has been defined). |