Web Performance Management (UltraWPM) uses custom "HTTP" status error codes to indicate connectivity-related issues with an HTTP request. These are not genuine HTTP codes. These response codes appear in the HAR file, the load-testing database and also when TransactionStepObject.getStatusCode() is called in the Test Scripts API.
WPM Custom HTTP Status Code
|
Status Code |
Stage |
Description |
Cause |
HAR Error Message |
Load Testing Headers Message |
Notes |
|
901 |
DNS Lookup |
Indicates that the IP address of a host could not be determined. |
Unable to resolve hostname using agent’s name server. |
Unknown host |
|
|
|
902 |
Connect |
Signals that a timeout has occurred while connecting to a remove server |
The server never accepted the socket connection or the connection acknowledgement was otherwise never received at the client |
Connection timeout |
|
Connection timeouts usually after 21 seconds (on Windows) |
|
903 |
Connect |
Signals that an error occurred while attempting to connect a socket to a remote address and port. Typically the connection was refused remotely (e.g., no process is listening on the remote (address/port). |
The server refused the connection; sent a RST packet during the connection process. |
Confuse refused |
|
|
|
904 |
Any time |
Transaction has ended and the connection has terminated mid stream. |
A script error; the script timeout or the script reached the end of the file. |
Script finished |
|
|
|
905 |
Response Headers Read, content being streamed to browser |
The client (e.g., the browser) terminated the connection from the remote server. |
The proxy making the request received a response from the web server. Headers were sent to the browser but the browser stopped the connection while reading the content. This can happen under the following conditions: The client (e.g., the browser) decided it did not about the HTTP response and closed the socket (e.g. a 4xx-5xx type error message for a subframe). |
Client(e.g., the browser) socket closed |
|
|
|
906 |
Reading HTTP response form server |
The server closed socketed |
The remote server closed the socket connection. |
Socket closed |
The remote server failed to response to the client’s request. |
|
|
|
|
|
There is a problem parsing the first HTTP line. HttpClient is expecting something of the form: “HTTP/1.1 200 OK\r\n”. If an invalid header is returned (blank headers) |
|
|
|
|
908 |
Sending request to remote server or reading response from remote server. |
The socket was reset; the remote server forcibly terminated the connection. |
Usually sent by the OS when the server process is killed or abort() is called on the socket on the remote server side. |
Socket reset |
|
|
| 909 | Sending request to remote server or reading response from remote server. | The socket timed out while sending or receiving data from the server. | The server responded to the connection request but took too long to accept our HTTP request or only partially responded to the HTTP request. The number of content bytes returned and response headers will appear in the HAR if there are any. | Socket timeout | Socket timeouts are set to 60 seconds by default | |
| 910 | After connect during handshake | SSL handshake error occurred | Either the client or server decided that the other end of the connection either: Had a bad certificate Did not support a compatible protocol The detailed message should hint at what the problem was. |
Received fatal alert: handshake_failure at... / Remote host closed connection during handshake at... | Note that connection resets, closes and timeouts are just as common here. The server may just abruptly end the connection when a client tries to connect with a bad cert or using the wrong SSL protocol. Other times the SSL engine (e.g. OpenSSL) on the server can just hang until there is a timeout. | |
| 911 | Before request was made to server | Bad URI | A URL requested by the browser or by the script is not a valid URL. | Bad URI | ||
| 988 | Any stage | An error occurred that we don't have an explicit error message for | Full description of the Java exception that was raised | |||
| -988 | Any stage | This is different from a positive 988. Possitive 988 are unanticipated exceptions that are caught, however with a negative 988 the exception was never caught and the details about the request may have been lost. | ||||
| -666 | Before request is made | Abuse detected | The request is blacklisted as an abusive URL on our network | Abuse detected |