Response timeout/slow response time: How can I distinguish between a network or application issue?
During the execution of each HTTP(S) request, the "internal processing states" of the HTTP(S) request are also captured by ZebraTester. In case of a response timeout - or when slow response times are measured - such an error is only a network problem (firewall, router, insufficient network throughput, loss of TCP/IP packets) if the error occurs at the internal HTTP(S) processing states "Open Network Connection", or "Receive HTTP Header", or "Receive Content".
If a response timeout or slow response times are measured at the HTTP(S) processing state "Wait for Server Response" the error occurred because the web application responds too slowly. This is the most typical case.
The following "internal processing states" of each HTTP(S) request are measured by ZebraTester:
* = the time elapsed in milliseconds for the corresponding processing state if no error occurs for each successful executed HTTP(S) request.
Please sign in to leave a comment.