HTTPClient never times out even with Timeout set on initiation
k0ngoz opened this issue · comments
In the executeCommand
function, the HTTPClient timeout is not being respected.
On WD initiation I run
// custom http timeout
var netClient = &http.Client{
Timeout: time.Second * 120,
}
selenium.HTTPClient = netClient
Try passing more args in the httpClient next to Timeout