Advanced Parameters - End Conditions
End condition
task timeout
① It ends normally. Visiting a page, executing a process, and pinging a domain name are all task contents. Each execution is a task. Taking the page as a task example, the page receives Onload Time as the end condition. Therefore, when the page is accessed again, Onload Time is received, indicating that the access to the page is completed and data is returned.
② Abnormal end, Onload Time has not been received. The client cannot wait forever, so there is a hard end time for the task. The default is 120s and the maximum is 300s. If Onload Time is not received after the preset timeout period, the task is forcibly ended and a Error is returned: "task Timeout" Error.
Note: Probe receives tasks, completes tasks, and uploads data. Among them, receiving tasks and uploading data are basically at the millisecond level, so here Total Download Time=end time
Extra Wait Time
No Wait Time is added, as shown in the figure, the error operation times out, and Element monitoring is incomplete.
The data after adding the Wait Time, as shown in the figure, Element is fully loaded
Client Redirect Count
There is an informal way to quickly know how many redirects there are. Visit the page with the browser, go to the "Network" file type and select doc. If there are several doc element, you will be redirected several times.